KINDRED
Create a gift

How it works

From an idea to something they open

Making a gift takes a few minutes. There are four steps, and each one shows exactly what the recipient will see.

01

Choose what you want to give

Six categories — experience, invitation, help, promise, something tangible or a money gift — plus the option to describe your own. A separate row of card styles shows how it could look.

02

Write the details

A name, a card message, and only the fields your scenario genuinely needs. A promise asks for terms; an invitation asks for a date and a place.

03

Choose who it is for, and how it looks

Recipient, visual theme and access rules. The live preview updates as you type, so nothing is a surprise.

04

Review and publish

You see the full page the recipient will open. Publishing creates the gift and a link you can send however you like.

Create a gift

For the recipient

Opening a gift should be the easy part

  • They open one link

    No account is needed to read it. The card comes first, then the practical detail and the conditions.

  • They accept or decline

    Either action is recorded honestly in the gift timeline — a decline is not an error state.

  • The status moves

    Sent, opened, accepted, declined. You both see the same thing, which is the point.

Wallet and payment

How sign-in and USDC are designed

Wallet sign-in and USDC payments are implemented. Here is exactly what they do, and what they deliberately do not.

Wallet sign-in (SIWE)

  1. 01You press Connect wallet; the browser reveals only a public address.
  2. 02The server issues a one-time nonce.
  3. 03You sign a message bound to this domain, the address, the nonce and a time limit.
  4. 04The server verifies the signature, the nonce, the domain, the time and the network.
  5. 05Only then is a secure session created.
  • · A plain signature never moves funds.
  • · Seed phrases and private keys are never requested.
  • · Signing in never requires a transaction or a paid signature.
  • · A connected wallet and a signed-in session are two different states.

Creating a gift (USDC)

  1. 01The server works out the fee — a creation fee plus the token issuance fee — and holds a record of it with the network, destination and expiry. The figure never comes from your browser.
  2. 02You check the breakdown, the network and the destination.
  3. 03You confirm the transaction in MetaMask.
  4. 04The hash is stored — but a hash alone is not a successful payment.
  5. 05The server verifies the network, the official token contract, sender, recipient, exact amount, receipt and finality.
  6. 06Only then does the payment become Confirmed, and only then does the gift become shareable.
  • · Kindred charges for creating a gift and for nothing else. It never collects or forwards the gift's own amount.
  • · Every kind of gift costs the same to create, a money gift included.
  • · A confirmed transfer cannot be undone by changing a database row. Refunds are a separate operation, not a status change.
  • · Kindred does not guarantee that a gift is fulfilled and cannot enforce it — that is the author's responsibility alone.

Test networks only

Your wallet is asked to approve one USDC transfer for the creation fee, and it is sent from your own account to the platform — Kindred never signs for you and never holds a key. While Kindred runs on a test network, no real funds are involved.

Ready when you are

You can draft and preview as much as you like before publishing anything.

Create a giftBrowse ideas