Skip to content

added stablecoin gas demo - #79

Open
soheimam wants to merge 5 commits into
mainfrom
feat/update-demo
Open

added stablecoin gas demo#79
soheimam wants to merge 5 commits into
mainfrom
feat/update-demo

Conversation

@soheimam

Copy link
Copy Markdown
Contributor
  • Added 8130 account creation in demo
  • Added b20 stablecoin gas payment

@cb-heimdall

Copy link
Copy Markdown
Collaborator

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 0
Sum 1

@vercel

vercel Bot commented Aug 20, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
omni-ui Ready Ready Preview Aug 25, 2026 7:59pm

Request Review

@montycheese montycheese left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

awesome demo, really slick improvements on v1! some feedback:

during the 'create token step'

Image this recent activity updating in real time super slick, I think adding more context to 'configuring [token name 1/2]' could be useful for developers, especially as they'll need to implement those steps on their end

one thing that isn't immediately clear (to me as well) is what checking the batch approve+ transfer step do. Because if I leave it unchecked, it does the transfer, it doesn't request a separate approval step before. Could be useful to add more context to that
Image

montycheese
montycheese previously approved these changes Aug 21, 2026
@cb-heimdall

Copy link
Copy Markdown
Collaborator

Review Error for montycheese @ 2026-08-21 15:16:35 UTC
User failed mfa authentication, see go/mfa-help

…s batches

Two problems reported after the rebase onto main's account engine.

The activity log moved into the shared bottom drawer, which is sticky and
full-bleed, so it read as a separate panel rather than part of the page. B20
narrates multi-transaction flows and the log has to stay readable next to the
form that started them, so it goes back to an inline card and the drawer in
AccountDemoShell becomes optional.

Creating a token failed at the configure step. sendBatches looped over
sendActiveCalls, and signComposed re-reads the nonce and probes for code on
every call. The public RPC is load-balanced across replicas whose heads can
differ, so the read between two sends can answer from a replica that has not
seen the first one: the second transaction is signed with the same nonce and
dropped as a duplicate. sendActiveCallsBatches reads both once up front and
counts each batch's sequence from there.
Creating a token from a new account failed on the second transaction with
"actor is not bound" (surfaced as "Missing or invalid parameters"). An
account's code and the actors bound to it reach every RPC replica a moment
after the transaction that wrote them lands, so the batch prepared right
behind the one that deployed the account was validated against a replica that
had not seen it yet and was rejected before it was ever broadcast.

Occasionally a later batch was broadcast and then dropped instead: the engine
signs at a flat 1 gwei maxFeePerGas, which equals the current base fee, so the
transaction carries no priority fee and is not guaranteed a slot.

sendActiveCallsBatches now retries a batch on both. A rejection before
broadcast waits for the state to propagate and signs again on the same nonce.
A broadcast that has not been included gets a longer wait, then the node is
asked whether it still holds the transaction — one it has dropped is sent
again, one it still holds is left alone so a second copy cannot collide with
it. The receipt-and-phase check that broadcast8130 already did moves into
awaitInclusion so both paths share it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants