More useful ideas

[Keith-CY]

I've got these thoughts during reading https://mirror.xyz/vanishk.eth/MTwltQDrHZenEPaFB9YsnScHVREmA3EWfLW-r9VguXs

It's just a TODOs now, and I will enrich each one ASAP.

---

What we have, but can be better

• State synchronization
• Message relaying
• General purpose indexer
• Plugin system
• Expressive query language

What we can add

• Development Dashboard: I've used similar functions in Elixir, https://github.com/phoenixframework/phoenix_live_dashboard, it's useful to locate performance bottlenecks and debug on production/development environments.
• Hot reloading: Enable hot-reloading in development mode, as https://docs.nestjs.com/recipes/hot-reload
• Type generation
• Built-in account abstraction: as discussed in wallet-connect protocol, there are two types of account, 1 from the perspective of a wallet, and 1 from the perspective from a dapp. For project built by kuai, we may consider supporting account from dapp perspective natively. The key point is how to map a bundle of addresses to an account in the backend natively.
• Local tx simulation: Dump the state and run tx sequentially to rehearse the actions on-chain

[Keith-CY]

Extension for built-in account abstract:

Built-in account abstraction: as discussed in wallet-connect protocol, there are two types of account, 1 from the perspective of a wallet, and 1 from the perspective from a dapp. For project built by kuai, we may consider supporting account from dapp perspective natively. The key point is how to map a bundle of addresses to an account in the backend natively.

Here's a concrete implementation

Sync account between frontend and backend

sequenceDiagram
    participant Frontend
	participant Backend
    Frontend ->> Backend: sync_account(10 addresses)
    Backend ->> Backend: store 10 addresses to account_id
    Backend ->> Frontend: account_id
    Frontend ->> Backend: get_balance(account_id, latest_address_in_frontend)
    Backend ->> Backend: compare_latest_addresses(latest_address_in_frontend, latest_address_in_backend)
    alt is false
    Backend ->> Frontend: account_info_out_of_date(latest_address_in_backend)
    Frontend ->> Backend: sync_account(addresses_diff_between_frontend_and_backend)
    Frontend ->> Backend: get_balance(account_id, latest_address_in_frontend)
    end
    Backend ->> Frontend: balance_of_address_from_address_0_to_latest_address    

Loading

The latest_address_in_frontend works as a session token that will be verified in backend with latest_address_in_backend, and time the session token out if latest_addresses in frontend and backend don't match.

[Keith-CY]

There's another strategy to calibrate the address set without binding to an account.

sequenceDiagram
    participant Frontend
	participant Backend
    loop
    Frontend ->> Frontend: H = Hash(Address set)
    Frontend ->> Backend: get_balance(H)
    Backend ->> Frontend: H is not found
    Frontend ->> Backend: subscribe_address_set(address set)
    Backend ->> Backend: H = Hash(Address set)
    Frontend ->> Backend: get_balance(H)
    Backend ->> Frontend: balance of address set H
    Frontend ->> Frontend: address set grows to address set'
    Frontend ->> Frontend: H' = Hash(Address set')
    end

Loading

By this idea, account id can be avoided and epherel address set will be registered in backend with its hash

[Keith-CY]

There's another strategy to calibrate the address set without binding to an account.

sequenceDiagram
    participant Frontend
	participant Backend
    loop
    Frontend ->> Frontend: H = Hash(Address set)
    Frontend ->> Backend: get_balance(H)
    Backend ->> Frontend: H is not found
    Frontend ->> Backend: subscribe_address_set(address set)
    Backend ->> Backend: H = Hash(Address set)
    Frontend ->> Backend: get_balance(H)
    Backend ->> Frontend: balance of address set H
    Frontend ->> Frontend: address set grows to address set'
    Frontend ->> Frontend: H' = Hash(Address set')
    end

Loading

By this idea, account id can be avoided and epherel address set will be registered in backend with its hash

Solution confirmed, technical details available at #554