• Nodes, edges, and walkers can all have abilities.
  • Abilities cannot interact outside of the context or local variables of the attached node, edge, or walker, and does not have a return.

An example of this would be a maintainer walker saving a user's id and last conversation state for continuing the conversation at a later time.

Saving state with a maintainer walker:

can cleanup with talker entry{
    if (!vistor:hoping) {
       spawn *(global.node_conv_root_state) walker::maintainer(
            user_id = visitor.user_id,
            user_context = vistor.user_context,
            dialogue_context = vistor.dialogue_context,
            last_conv_state = vistor.state_for_continuing
            /// @dev Add ERC-4337 account abstractions or any other saved states, etc here.
       );
    }
}

• 🔭 I’m currently working on Digital Intelligence PWA's: DIDEGGO, DAO - Digital Intelligence Decentralized Global Governance, Decentralized Autonomous Organization, and Apexmite Content Federation

Artist: WrappedUsername + DreamStudio

Artist: WrappedUsername + DALL*E

• 👀 Are you currently looking for a 🕸 web3 blockchain job or other dev jobs? Check this out! Developer Jobs Here!

  • Yes this is an affiliate link to help me earn money!

• 🚀 Active in production Foam Chunk Smudge NFT, Portfolio Website, and Journey Blog

I *was* trying to learn all of this non-sense all at once:

• Vercel
• TypeScript
• Next.js 13
• React
• Tailwindcss (switching to pure CSS)
• Sass
• Angular

• Open and Internal
  • JSON-RPC
  • GraphQL
  • REST

• Nest
• Express
• GraphQL
• Hygraph CMS
• MySQL
• GCP Firebase

• Oracle VM VirtualBox
• Kali Linux
• Python

• Google Analytics

• Docker
• Python
• TensorFlow
• GCP
• IBM Watson Studio
• Azure
• Oracle AI

• REMIX IDE
• Hardhat
• TypeScript
• Solidity
• Ethers.js
• Python for testing (echidna fuzzer)

• Python (I am researching this for modeling)