Understand it.
Make it yours.

The basics

RecallBond is a system for registering products with a transferable digital passport. A manufacturer issues a passport for a device. When the device changes hands, the passport can be transferred to the next owner. If a manufacturer recalls that product's batch, the eligible current owner can claim compensation from a reserve that the manufacturer funded in advance.

How the system works

1. A registered manufacturer issues a NEAR digital product passport.
2. The product owner receives the passport in their NEAR account.
3. When the product changes hands, the passport can be transferred securely.
4. If a recall happens, the manufacturer deposits the full potential compensation before activating the campaign.
5. The eligible current owner claims once and withdraws the approved testnet NEAR credit.

For product owners

The intended consumer experience is a mobile-first account with email/password sign-in and a NEAR wallet associated with the user's profile behind the scenes.

1. Sign up. Create your RecallBond account. Secure account creation and automatic wallet provisioning are planned; they are not yet implemented in the current static browser demo.
2. My products. View registered product passports and any available recalls. The current interface contains labeled sample records, while read-only testnet verification is genuinely live.
3. Transfer. Hand the onchain passport to the recipient's NEAR account. Ownership changes only when a valid wallet-signed blockchain transaction succeeds.
4. Report an issue. Describe a defect and follow review status. The current defect-report experience stores browser-local demonstration data, not real manufacturer support tickets.
5. Claim and withdraw. A current holder of an eligible passport may claim from an active, fully funded campaign. Contract credit and spendable wallet funds are distinct until withdrawal succeeds.

For manufacturers

Manufacturers will have an authenticated company workspace with roles, product issuance, inventory, recall management, reports and customer requests. The hackathon example uses the fictional NovaTech manufacturer.

1. Register the business. The planned onboarding will verify company details and associate a NEAR issuer account with authorized personnel. Company self-registration and identity verification are not yet live.
2. Issue passports. Registered issuer accounts can mint real NEAR testnet passports through the deployed contract.
3. Manage recall campaigns. Select a batch, define a per-passport payout, and deposit the entire maximum liability before activating the recall.
4. Review issues. A secure database-backed support inbox is planned. The current claim-review UI is a browser-only demonstration.
5. Track results. The dashboard includes live public blockchain reads and links to receipts for verifiable contract operations.

Accounts & wallets

Our product goal is simple: sign in to RecallBond, and your NEAR account is already linked. Ordinary people should not have to understand seed phrases, blockchain address creation or wallet connection just to start using the application.

Planned seamless onboarding

1. Person creates a verified email/password account.
2. A secure embedded-wallet provisioning service creates or assigns a NEAR account and links its public account ID to their profile.
3. Every sensitive action is authorized by the account holder with an authenticated, appropriately scoped signing mechanism.
4. The wallet page shows the address, balances, transaction history, security controls and a safe recovery/export workflow where applicable.
5. A company can authorize staff with role-based permissions without giving everyone the main issuer's private key.

This will require server-side sessions, secure account storage, transaction signing infrastructure, recovery policies and testnet gas sponsorship. We will not put unencrypted private keys in the database, local storage or frontend source. Email/password authentication alone does not make a blockchain signing key safe.

Security and privacy

• Onchain data is public. Account IDs, token transfers, recall funding and claims can be inspected by anyone on NEAR testnet.
• Protect user information. Names, emails, phone numbers and raw product serials should remain offchain. The contract stores a salted serial commitment rather than the raw serial.
• Wallet control matters. Signatures must come from an authorized account or a properly secured delegated signing service. A profile display is not authorization.
• Compensation is reserved. Active recalls must be fully funded; a single passport can only receive one claim per campaign.
• Prototype disclaimer. This is hackathon software on testnet. It is not audited and does not issue a legally binding warranty.

Live testnet proof

Our public verification surface reads the deployed contract rb-vk97-261112.testnet and passport RB-NV-002891. The example manufacturer, people and device are fictional, but these blockchain operations genuinely occurred on NEAR testnet.

1. Mint the NovaBook Air passport to Ada
2. Transfer ownership from Ada to Tomi
3. Fund the recall with 0.1 testnet NEAR
4. Tomi's successful compensation claim
5. Rejected duplicate claim
6. Finalized payout and successful callback

The failed former-owner and duplicate transactions had generic WASM trap messages. State verification showed the wrong owner received no credit and the second claim did not change the recorded claim count or payout. See the complete evidence log.

Short glossary