Web 3.0 | Aerospace Engineering Student | Smart contract developer | Security researcher | ZK Engineer | Building @DeCipherLabs_HQ
Joined September 2024
- Tweets3.1K
- Following296
- Followers233
- Likes4.2K
So this is where Sealed stands:
Contracts deployed. CLI auction lifecycle exercised. Winner payout and loser refund tested.
Browser bidding remains blocked. Sponsored transactions are unverified, claims need redesign, and several contract edge cases still need testing.
@azguardwallet: what Aztec version and verification-key format does the current build support? Is v6 compatibility available or planned?
@aztecnetwork: could you point me toward the right compatibility guidance?
@Zac_Aztec Please I need your guidance on this too.
I can share the exact error and reproduction details. A reply or retweet would help.
After fixing an artifact-parsing error, I reached a new blocker.
Azguard fails during capability negotiation with:
verification key has wrong size: expected 5216, got 4832
I reproduced it twice. The browser auction still cannot get past this stage.
Even if the wallet issue is solved, claims have another design problem.
Winner and loser payouts require the claimant's PXE to register the auction's secret and include the auction in additional scopes. The wallets tested do not expose that setup.
But I have not isolated which registered contract triggers the error. A wallet compatibility issue is possible, not confirmed.
I checked the frontend's Aztec package versions, compiler version and verification keys. They are consistent with one another, and the CLI flow works on the same deployment.
Then I tackled transaction fees.
Fresh browser accounts have no Fee Juice, so I integrated the Sponsored FPC artifact, added fee payment options to transaction calls and updated the capability manifest.
The frontend builds, but browser sponsorship is still unverified.
The migration was not just changing package versions.
I redeployed the auction and token, updated frontend configuration, dealt with RPC timeouts, IPv4/IPv6 issues and batch-size limits, then rebuilt the frontend around the new testnet.
I migrated Sealed to @aztecnetwork v6 to escape one wallet compatibility issue. Now I am facing another.
Contracts deployed. CLI auction lifecycle tested. But Azguard rejects our verification keys before I can test bidding in the browser.
Here is the full story. 🧵
I've been building Sealed, a private auction app on @aztecnetwork. A lot has happened since my last update, and I've been digging into a browser integration issue that's holding up the next stage.
@Zac_Aztec, I'd appreciate your eyes on this too.
Here's the progress so far. 🧵
Back at it with the RC helicopter in CATIA V5. 🚁
This time, I worked on the back propeller, back rod, fin side wing, and one of the subassemblies for the rear section.
Slowly bringing the different sections together.
It’s been a while since I last worked on my RC helicopter assembly in CATIA V5, but I’m picking it up again.
Last worked on the back wing, tail shaft, fin mount holder, back wing mount connector, back motor holder housing, and one of the subassemblies.
Slowly getting back...
Tactful Cipher retweeted
There's no way people won't get turbo pilled on programmable privacy once they understand you can execute private smart contracts without ever deploying their code onchain.
Read again.
You can execute an entire smart contract without its code ever touching the blockchain 🤯
I've been building Sealed, a private auction app on @aztecnetwork. A lot has happened since my last update, and I've been digging into a browser integration issue that's holding up the next stage.
@Zac_Aztec, I'd appreciate your eyes on this too.
Here's the progress so far. 🧵
The last time I posted about Sealed, I was still trying to get the auction flow working on @aztecnetwork testnet.
A lot has happened since then. I’ve now taken two listings through settlement and successfully claimed both winning bids.
Let me show you where I’m at. 🧵
I'm asking because resolving this would help me move from successful CLI tests to testing the actual auction experience through the browser.
If there's a known compatibility requirement or someone who can point me in the right direction, I'd be grateful.
I'm committed to getting Sealed working properly, not just making a demo look complete.
There's been real progress, but I'm at a point where guidance from people familiar with the @aztecnetwork and @azguardwallet internals could make a real difference.
Still building.