October Build Contest Thread: Spooky Secrets!

Update to Séance (post #15). This is not a second entry. New accounts can only edit a post for 24 hours, so I’m adding the required items here:

Try it in your browser: https://seance.madebydevx.com
Announcement (Bluesky): @devxtools.margin.cafe on Bluesky
Tari payment address: 14DQWqt4gHNwH1t57o3ZVqy64bbqu1P3zDkH2sKEKqDqVhUVu4xWQD7pGGZm29nehPJ7DKgMUNTMNE8ZuudNRXHFosi

Full updated entry: SUBMISSION.md in the repo linked in post #15.

Graveyard Shift update: it’s live on Esmeralda :green_circle:

The confidential payroll template is now published on the Ootle testnet, and it has paid a real night shift:

Open the shift tx and you’ll see the events Hired, Hired, PeriodOpened {period: 1} and ShiftPaid {period: 1, paychecks: 2}. No amount appears anywhere. Reading the same outputs back from the public indexer:

  • the night nurse’s key opens only her stub: 3000, “12 nights, ward 13”
  • the gravedigger’s key opens only his: 2500, “9 plots, lantern allowance”
  • the auditor’s view key reads 3000 + 2500 + 4500 treasury = 10,000 = the public budget :check_mark:

The faucet was dry, so I funded this by CPU-mining Esmeralda and burning tXTM over the burn/claim bridge. The whole deployment cost about 1.5 tTARI in fees. examples/live_esmeralda.rs in the repo builds the transactions and re-runs that check against the indexer, so anyone can reproduce it.

Code: GitHub - XachP/graveyard-shift: Confidential payroll template for Tari Ootle (Spooky Secrets contest entry) · GitHub · Browser demo: Graveyard Shift · confidential payroll on the Tari Ootle

Caravel Burn Wallet: a private, verifiable burn wallet on the Tari Ootle

Description
The Caravel Burn Wallet is a burn wallet on the Tari Ootle that anyone can use and anyone
can verify. The Council mentioned wanting to burn the fees generated from the initial
Ootle launch, so I built a burn wallet they (or anyone) can audit and use.

  • Deposit-only and ownerless: TARI can go in, but nothing can ever come out. No owner, no
    admin key, no withdraw function.
  • The total burned is public and verifiable on chain at any time.
  • Burns can be private: nothing ties a private burn to your account, but the amount is
    still counted in the verified total.
  • Any project can integrate it to burn a portion of its fees forever. Caravel Trade
    already burns 0.3% of every trading fee through it.

So far: 13,128.73 TARI burned. There’s also a 25,000 XTM bounty for anyone who can rug the
wallet: Caravel on X: "1/ New in Caravel ⛵ We've been cooking the @tari Ootle's first burn-centred game 🎲🔥 As that progresses, here's our next ecosystem contribution: the Caravel Burn Wallet. Deposit only, never withdraw ... Not even us. Think you can rug it? Winner takes all: 10,000 $XTM 😏 https://… / X

Links

Tari payment address
129Wf58tMXfYvqtQgQiuZbs8V75vGKKMPZGKSYVbQNvPDeHwaJ5VzjFXEhpsTEXs5NUbHm2JUVVum5Be1DKs1Zg9Sg7

1 Like

Caravel Trade: a private peer to peer OTC platform on the Tari Ootle

Description
Caravel Trade is a peer to peer OTC platform on the Tari Ootle that lets you trade TARI
using the Ootle’s privacy features. To support it, I created a test token, Caravel USD
(cUSD), as a placeholder for a future Ootle stablecoin.

  • Place a buy or sell order for TARI, priced in cUSD.
  • Non-custodial: your funds sit in the order contract, never with Caravel. Only you (by
    cancelling) or a matching trade can release them.
  • Orders fill whole in a single transaction, and you can cancel anytime.
  • Private by default: amounts and balances stay hidden, from placing an order to getting paid. You can choose public at any step.
  • 1% fee per trade, paid in TARI: 0.7% to Caravel and 0.3% burned forever through the
    Caravel Burn Wallet (my other entry).

Links

Tari payment address
129Wf58tMXfYvqtQgQiuZbs8V75vGKKMPZGKSYVbQNvPDeHwaJ5VzjFXEhpsTEXs5NUbHm2JUVVum5Be1DKs1Zg9Sg7

1 Like

@XachP @DevXTools

You should both now be able to edit your previous posts. Please do so and update your existing posts.

Anyone else who needs to do this, please reply to this comment asking for perms.