September Contest Thread

Project: Caravel

A Swiss bank account in your pocket.

For a century, a Swiss bank account meant one thing: your money was yours, and no
one else’s business. That privilege was for the few.

Caravel puts it in your pocket. Built on the Ootle, Tari’s confidential smart
contract layer, it’s the start of a private neo bank, expanding privacy services one
at a time. Nothing to install, and your keys never leave your device.

Live today:

Wallet. Hold funds privately or publicly, and disclose only when you choose. Send,
receive, and move between private and public at will, revealing only what you want.

Chat. Private messages and private money in one conversation. Messages are end to end
encrypted over Nostr and wrapped so relays can’t read them or see who sent them, with
payments built right into the chat.

Instead of sharing a raw key, you can register a @name through Caravel Name Service.
The name is registered on chain in a Tari Ootle template and tied to your Nostr
identity, so anyone can find you and start an encrypted conversation with a simple
handle.

How it works:

Everything happens on your device. One recovery phrase powers both your wallet and
your chat identity, and every transaction is signed locally in your browser, nothing
to install and no keys to hand over. Caravel talks only to public Ootle indexers and
Nostr relays, never a server of ours.

What’s next:

We’re expanding Caravel into the everything app for private finance. Our team is now
researching the feasibility of bringing wrapped assets onto the Ootle, giving Bitcoin,
Monero, and Zcash programmable privacy for the first time.

Screenshots:

Submission details

App: https://caravellabs.net

Code (open source, MIT): GitHub - okansaglam016161-pixel/caravel · GitHub

Tari payment address:
129Wf58tMXfYvqtQgQiuZbs8V75vGKKMPZGKSYVbQNvPDeHwaJ5VzjFXEhpsTEXs5NUbHm2JUVVum5Be1DKs1Zg9Sg7

Announcement post:

3 Likes

Big Usability Improvement:

v0.4 makes the android app stable and adds background trade processing.

To trade:
Go to WunschVouchers - Create demo voucher
Register (just username and password)
Create a voucher

Seller:
Go into App
Sell Voucher
Create offer with voucher Code

Buyer:
Go into App
Buy Voucher
Take Offer
Add your user Account (only needs to be done once can be changed in settings)
See your account balance increase on the site

Please anyone from the folks voting on the submissions try our app.
Reply to this if you only have on device we can also try together. Just give me a time you wanna do it

Bounties powered by Threshold — council-reviewed GitHub issue escrow on Ootle

What better way to show Ootle than to replace a bounty program used by the Tari team? That is the idea behind Bounties powered by Threshold, an independent proposal to bring the team’s GitHub issue bounties onto Ootle. This is my separate September entry alongside my earlier Threshold crowdfunding submission. The dedicated Rust/Ootle template funds one GitHub bounty issue per component. A static proof archive shows five examples recorded on the former Esmeralda testnet.

A designated council manager creates the issue record and sets one to five reviewer keys and a quorum, such as 1-of-1, 1-of-3, or 2-of-3. The manager can revise the scope and reviewer set before funding; funding freezes those terms. The demo treasury locks the exact fixed tier amount. Reviewers can approve an award after checking the GitHub work, including a split among contributors. An XL award also needs its configured steward quorum. There is no deadline: before an award, the same reviewer quorum can record a “no work” decision so the original treasury key can reclaim the full untouched escrow.

The demo used synthetic issue numbers, demo council identities, and faucet tTARI. Its five components included three open and funded when the saved snapshot was taken. A 1-of-1 no-work decision was followed by a full treasury refund. A 2-of-3 second approval was followed by a contributor claim. The offline archive bundles the saved state, reviewer keys, and receipts without needing the indexer.

The contract enforces funding, signer authority, reviewer quorum, and exact payouts. Council members still judge PR quality and supply digests of the off-chain evidence. The former Esmeralda chain was reset after this demo, so these records are historical proof, not current-chain balances or live components. This is an unaudited proposal, not an official Tari bounty program or a migration of its funds. The existing program pays XTM; this template uses Ootle-native TARI, so Tari would need to approve the policy and asset change before real use.

2 Likes

Ootle Surveys — September 30 reset update (v0.2.1)

We have redeployed Ootle Surveys on the reset Esmeralda network using Ootle 0.42. The encrypted questionnaires and private participation rewards are working again, including the survey workflow improvements from our September 26 update.

  • Current source and setup: verified v0.2.1 commit
  • Changes for review: updated PR #1 (still a draft; use the source link above for this version)
  • Current deployment and payout evidence: artifacts
  • License: MIT, with the included Tari burn-proof adapter attributed under BSD-3-Clause.

Fresh deployment

Template: template_0a92d6f2a1ab3a3789082a2efb525c6109300fd838e793eb97cd9bcb699deb85

Reward pool: component_fcf7b76f5ddcff9cc40a33e37de1a7b65a302bf7d02ddad8c01fafee0e3d93dc

The new pool was funded with 100 tTARI. Two real verification rewards have been paid, leaving 98 tTARI. Funding used an Esmeralda L1 faucet followed by a 200 tXTM burn and confirmed Ootle claim; the setup no longer depends on the old L2 faucet. The repository includes the funding and reset-recovery steps.

Verified after the reset

The complete browser flow passed: save/recover an encrypted draft, publish a questionnaire, open a private invitation, submit an encrypted response, decrypt it as organizer, approve participation, and confirm the private reward.

Both test recipients independently decrypted exactly 1 tTARI. Unrelated wallets could not decrypt their outputs. Repeating an approval returned the original transaction without another payment; rerunning the CLI verification also reused its existing payout.

Browser-flow payout: 9e84cf9d586f5415f77fab155361cfd54016ad0169249c3834e12eeaac5a4abf

The build, 12 automated Node tests, and four Ootle 0.42 engine tests pass. One optional legacy external-HTTP test is skipped; the self-contained HTTP lifecycle suite runs. The engine tests include rejection of mixed public/private payouts. Pre-reset deployment records are explicitly archived as historical evidence.

Questions and answers stay off-chain. The organizer can read responses and reward addresses; pool funding, fixed rewards and transaction timing remain public. This remains a self-hosted, single-organizer testnet application, without public hosting or an independent security audit.

Our prize-payment address and social announcement remain in the original entry.

1 Like

Where can I get new testnet funds, the faucet seems to be empty I cant deploy. Am I doing something wrong?

very nice project, quick question how did you get new testnet funds? could you spare some for me please or fund the faucet

otl_esm_1nzxnzzxknjfhuex3t4xxwmgszntzf7c3k4nh2m9huzgwewsdl4lagrp62kr32v98dy8sv2gfy3n8xp9rm5szfwzruaq4j5nalkyrujqfyzfke

999 tTari send, pls check.

2 Likes

Hey @urelamba ,

You can get tXTM from https://testnet-faucet.supportxtm.com/ and than follow this guide to get TARI on Ootle testnet : Burn Minotari for TARI | Tari Ootle Playground**
**
If you don’t have minotari cli you can use https://universe.tari.mw as a wallet to get the testnet L1 funds and burn them. **
**
I would highly recommend you try this as we are getting closer to ootle mainnet and need testing.

a good thank you for the hint. I assumed there was another faucet as before. That makes sense since its also how I will get funds on mainnet.

1 Like

v0.5

out now. please test

Thank you all for your submissions! The council will begin judging and announce the winners soon!

5 Likes