Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesIn the design Daniel Ioni describes in his September 16, 2026 DEV Community article, a MyZubster Marketplace request is created when a signed-in user proves control of an EVM-compatible browser wallet, reviews a snapshot of a listing’s economic terms, and signs a one-time payload. That signature authorizes the creation of a request record. It does not authorize a payment, it does not send a blockchain transaction, and it does not spend gas. The rest of this article explains how those separate pieces fit together, what the author reports as implemented, and where the evidence stops.
All implementation, test, and status details below are as reported by the author in that article. We have not independently reproduced the tests or confirmed the current state of the project. The original write-up is at https://dev.to/danielioni/building-signed-wallet-requests-for-the-myzubster-marketplace-3h2m.
As an Amazon Associate I earn from qualifying purchases.
How the flow runs, from account to request
The author breaks the path into five stages. Each stage produces a different kind of evidence, and the design keeps them apart on purpose.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →- Authenticate to a MyZubster account. The user signs in to the account first. The wallet is then attached to that account; it is not treated as the login itself.
- Connect an EVM-compatible wallet through an EIP-1193 provider. The browser wallet exposes its accounts through this provider interface. Connecting at this point only tells the application which address the browser can see.
- Prove wallet ownership. The backend issues a wallet ownership challenge containing a nonce and an expiry time. The wallet signs it with
personal_sign, the backend verifies the signature, and the wallet is associated with the account only if verification succeeds. - Create a Marketplace challenge for the listing. When the user wants to request a listing, the server builds a separate Marketplace challenge and a canonical payload. That payload includes a snapshot of the listing’s economics: price, currency, and exchange mode.
- Review and sign the payload. The user signs the payload. The backend verifies the signature, consumes the challenge, and creates an order in
REQUESTEDstate.
The author also lists example endpoints for each step, covering the wallet challenge, verification, current-wallet lookup, disconnect, the Marketplace order challenge, and Marketplace order creation. These are examples from the author’s own account. They should not be treated as a stable public API reference; check the project’s current documentation before building against them.
#1 Best Overall
- Effortlessly build your crypto portfolio via the all in one Ledger Wallet app: buy, sell, send, receive, swap, stake and more across popular blockchains. 15,000+ coins & tokens in a single dashboard. Keep a close eye on the market. Compare service providers. Track performance. Get timely alerts. Build your portfolio with confidence.
- Enjoy Bluetooth connectivity, iOS access, and hours of battery use with this mobile-first, secure backup signer. Freedom you can depend on.
- Genuine Check: confirm your signer is authentic during setup with the Ledger Wallet app.
- Protect your signer: keep it in mint condition at all times with a bespoke Pod or Case to avoid scratches and everyday wear and tear.
Connected is not the same as verified
The most useful distinction in the design is between a wallet that is merely connected and one that has been verified. The author treats these as two separate states.
| State | What it means | What establishes it | What it does not establish |
|---|---|---|---|
CONNECTED |
The browser wallet has exposed an address to the page. | The EIP-1193 provider returns an account. | That the logged-in user controls the address. |
VERIFIED |
The backend has checked a signature over a fresh nonce and linked the address to the account. | A valid personal_sign response to the ownership challenge, checked by the backend before the link is stored. |
That the account has paid, is an accepted seller, or has any Marketplace order. |
The reason for the split is practical. A provider can report an address, but that report alone cannot show who is holding the keys. Only a signature over a server-issued challenge does that, which is why the ownership challenge carries a nonce and an expiry rather than a fixed message.
Signing a listing request: the canonical payload
A verified wallet does not automatically authorize a request. For each listing, the server builds a separate Marketplace challenge and a canonical payload. The author says the payload binds the request to the listing’s economic terms as they were when the user reviewed them: price, currency, and exchange mode.
That binding matters because listing terms can change between the moment a user reads them and the moment the request is submitted. The author’s design rejects that case instead of silently accepting the new terms. If the listing snapshot differs from the one in the signed payload, the server returns MARKETPLACE_LISTING_CHANGED, and the user must review the current terms and sign a fresh challenge.
The UI text the author quotes, shown before signing, makes the limits of the signature explicit:
“This signature creates a Marketplace request. It does not authorize a payment. It does not send a blockchain transaction. No gas.”
Rank #2
TANGEM Crypto Wallet Pack of 2 – Trusted Cold Storage Hardware Wallet | 100% offline; Bitcoin, Ethereum, NFTs & altcoins; No seed phrase; NFC, Self custody wallet
- Seedless by design, nothing to steal: Your private key is generated inside the EAL6+ chip and never leaves it. No seed phrase is shown or typed at setup, so a tampered device, keylogger, or phishing site has nothing to capture. 9+ years, millions of card.
- Tap once to manage your entire crypto wallet across 90 blockchains - no USB cables or Bluetooth, no batteries, no setup. Access 16,100+ coins & tokens, DeFi, NFTs, and staking instantly from your phone
- Backup without a seed phrase: Your wallet is copied to 2 backup cards with end-to-end encryption, so there are no words on paper to lose or leak. Keep them in separate places; if one card is lost, the others restore full access. Optional seed phrase for advanced users.
- Engineered to last up to 25 years: Waterproof (IP69K), shockproof and tested for extreme temperatures from −25°C to 50°C. A durable cold wallet with long‑term protection and independently audited security.
- Trusted by 6 million users worldwide - buy, sell, swap, stake, and spend cryptocurrency directly. The secure offline storage wallet designed for how people actually use crypto wallets
The author frames the review step around six questions a reader can use to check any similar design:
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match- Which authenticated account created this request?
- Which wallet controlled by that user signed it?
- What listing was being requested?
- What were the economic conditions at the moment of signing?
- Has the same authorization already been used?
- Did the listing change between review and submission?
Challenge lifecycle: one authorization, one request
Each challenge is designed to be used once. The author describes a lifecycle with an expiry, a consumed state, and separate handling for three failure cases: an expired challenge, a challenge that was already consumed, and an invalid signature. In each case the request is refused and the user must start again from a new challenge rather than reusing the old signature.
This is the replay protection the author lists as implemented. It addresses one specific risk: a captured signature being submitted again to create a second request. The author’s account does not describe a broader threat model beyond that.
Atomic creation: consume and create together
The author moved challenge consumption and order creation into a single database transaction. The stated goal is that the authorization is spent and the request is created together, or neither happens. A failure between the two steps should not leave a consumed challenge without an order, or an order created from a challenge that was never marked used.
Notifications are sent after the transaction commits. The ordering matters: a notification about a request should not be sent for a request that was rolled back. The author’s test list includes transactional creation as one of the covered areas, but the write-up does not describe the database engine or isolation settings, so those details should be checked against the actual implementation.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What the signature does not do
The design depends on keeping several things separate. Read each of these as a boundary, not a limitation to be fixed later in the same signature.
Rank #3
- UNPARALLELED SECURITY: Protect your assets with Trezor Safe 5's NDA-free EAL 6+ Secure Element, offering robust defense and complete transparency.
- EFFORTLESS NAVIGATION: Experience seamless crypto management with the vibrant color touchscreen, designed for intuitive and user-friendly interactions.
- ENHANCED USER EXPERIENCE: Enjoy tactile confirmation with Trezor Touch Haptic Engine, making each interaction precise and engaging.
- SUPPORTS 1000s OF COINS & TOKENS: Securely handle thousands of assets, including Bitcoin, Ethereum, and more, all in one wallet.
- EASY ASSET MANAGEMENT: Monitor and transact seamlessly with Trezor Suite, our user-friendly desktop and mobile app
- A Marketplace request signature is not payment authorization. Signing the request authorizes a request record to be created. Money movement is not part of this flow.
- The request flow does not submit an on-chain transaction or spend gas. The author states this directly in the pre-signing copy quoted above.
- A verified wallet is not a paid seller. Verification proves control of an address. It says nothing about payouts, sales, or account standing.
- A
REQUESTEDorder is not anACCEPTEDorder. The request has been recorded; it has not been accepted by the other party.
| Object | What it records | Created by | Blockchain involvement |
|---|---|---|---|
| Wallet link | Control of an address by an account | Ownership challenge and verification | None in the request flow |
| Marketplace signature | The user’s approval of a specific listing payload | personal_sign over the canonical payload |
None; no transaction and no gas |
Order in REQUESTED |
A request exists in the Marketplace system | Order creation after signature verification | None described |
| Payment | Not part of this design; described as future work | Not stated | Not stated |
| Anchored evidence | A digest that can show digital data was anchored | A separate evidence lifecycle, potentially after a Marketplace activity is completed | Yes, by design of the anchor |
Optional blockchain evidence is a separate path
The author describes anchoring a digest on a blockchain as a distinct lifecycle, not as part of the buyer’s request signature. In the described design, it may happen later, after a Marketplace activity is completed, and it creates a record that some digital data existed in a particular form at a particular time.
That is all an anchored digest establishes. It does not, by itself, prove a physical event occurred or verify an environmental claim about a product or service. Any Marketplace feature that relies on anchored evidence for a physical or environmental statement would need its own verification step.
Reported status at publication
The author marks the following as implemented as of the September 16, 2026 article. This is the author’s own status, reported at that date. We have not checked whether it has changed since.
| Area | Status reported by the author |
|---|---|
| EVM wallet linking | Implemented |
| Wallet ownership verification | Implemented |
| Replay protection | Implemented |
| Signed requests | Implemented |
| V2 economic snapshots | Implemented |
| Transactional request creation | Implemented |
| React request flow | Implemented |
| Public production deployment | Pending |
| Public wallet end-to-end testing | Pending |
| SIWE-style domain binding | Pending |
| Production rate limiting | Pending |
| Real payment onboarding | Described as a future phase |
The author reports six backend test suites and 25 passing tests. The suites cover the wallet signature service, challenge consumption, the signed request service, transactional creation, an end-to-end flow, and Marketplace lifecycle coverage. The author also reports browser tests for a successful request, an existing verified wallet, a newly verified wallet, a rejected user signature, a missing provider, changed listing economics, and a request that avoids sending an Ethereum transaction. The React production build is reported as completed.
These counts describe one project’s own test suite at one point in time. They are not a benchmark or a general measure of security or reliability.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Failure handling a builder should expect
The author’s design has explicit responses for the cases below. The user action column reflects what the flow requires, based on the behavior the author describes.
Rank #4
- Dual-chip architecture for maximum protection: The next-gen, fully auditable TROPIC01 chip works alongside a certified EAL6+ Secure Element—completely NDA-free—to deliver radically transparent, industry-leading defense against physical attacks.
- Quantum-ready security: Get protection against future threats with the first-ever hardware wallet designed with quantum-ready architecture.
- See every detail with confidence: Our largest high-resolution color touchscreen makes it easy to navigate your assets, review transactions and manage your coins with clarity.
- Wireless freedom with encrypted Bluetooth control: Manage, buy, swap and stake securely using Trezor Suite on desktop or mobile. Qi2-compatible wireless charging keeps your Trezor powered up. No cables required—security meets convenience.
- Works seamlessly with Android, iOS and desktop: Connect wirelessly or via USB-C to your phone or computer. Manage your crypto anywhere with our companion Trezor Suite app.
| Condition | Reported behavior | What the user does |
|---|---|---|
| Challenge expired | Refused as expired | Start a new challenge and sign again |
| Challenge already consumed | Refused as previously used | Start a new challenge; the old signature cannot create another request |
| Invalid signature | Refused; no order created | Sign again from a fresh challenge |
| Listing economics changed | Rejected with MARKETPLACE_LISTING_CHANGED |
Review the current terms and sign a fresh challenge |
| No EIP-1193 provider found | Covered by a browser test for a missing provider | Use a browser wallet that exposes an EIP-1193 provider, then reconnect |
Comparing this design with alternatives
The article describes one architecture rather than competing products, so there is no direct product comparison to make. If you are evaluating another implementation of the same pattern, these six questions separate the approaches that matter:
- How wallet ownership is verified, and whether it is verified before the address is linked to an account.
- Whether challenges carry a nonce and an expiry, and whether they are consumed exactly once.
- Whether the signed payload binds the listing’s economic terms, so a change is detected instead of silently accepted.
- Whether challenge consumption and order creation are atomic.
- Whether the signed message is bound to a domain or origin, and whether requests are rate limited.
- Whether intent, payment, order state, and on-chain evidence are kept as separate records.
On the last two items, the author lists domain binding and production rate limiting as pending. A reader should not assume either is in place in MyZubster’s current deployment based on this article alone.
Future payment work is design discussion
The author discusses a free-first Marketplace direction and describes what payment work would require: onboarding, payouts, refunds, disputes, webhooks, compliance boundaries, and fee transparency. These are presented as the author’s roadmap and design considerations. None is described as a completed production capability, and the article does not give a timeline for them.
For builders, the practical point is that the current request flow is designed so that adding payment later would be a separate authorization and a separate record. Keeping intent, payment, order state, and evidence apart now is what makes that later work tractable.
Source: Daniel Ioni, “Building Signed Wallet Requests for the MyZubster Marketplace,” DEV Community, September 16, 2026: https://dev.to/danielioni/building-signed-wallet-requests-for-the-myzubster-marketplace-3h2m
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
