Tari Local Opensource Swap Platform

Development
1

Hello everyone,

I have been around since testnet and see the long term vision for Tari. I HODL my XTM.

I’ve been working on a local-first Tari/Ootle atomic swap and asset testing app, and I wanted to ask what people here would actually want from something like this.

It’s still early and experimntal, but the goal is to make Tari L2 easier to test and use without needing a hosted exchange or giving custody of funds to anyone. After that, mainnet with the same vision.

The idea is a simple local UI where people could test atomic swaps, TARI flows, public test assets, NFTs, and eventually cross-chain routes. I’m also working toward better two-person swap flows using invite/export/import features and QR codes, so sharing a swap invite or wallet info is not just copying giant addresses back and forth.

The branding is cat-themed and memeable because I think Tari could use something fun and approachable, not just another serious DeFi dashboard. The style is playful, but I’m trying to make the tool actually useful.

Things I’m thinking about:

  • Local-first atomic swap UI

  • tTARI testnet swaps

  • Test asset creation/distribution tools

  • NFT testing and swap support

  • QR-code swap invites and wallet sharing

  • Better wallet/indexer status and error messages

  • Beginner-friendly setup guides

  • Possible YAT support later

  • Future cross-chain testnet routes

  • Future local-first liquidity/pool testing

To be clear, this is not a token sale, investment product, hosted exchange, or anything where users deposit funds into a centralized service. I’m aiming for open-source local tooling.

Longer term, if it becomes useful, I may look at optional donations or community grants to support development. I do not want the app to depend on forced platform fees or custody of user funds.

A few questions:

  1. What would you want from a Tari atomic swap/testing app?

  2. Would you care more about swaps, test assets, NFTs, QR-code invites, liquidity tools, or cross-chain routes?

  3. What feels most confusing right now with Ootle walletd, templates, ResourceBuilder assets, or testnet flows?

  4. Would beginner guides and easier local setup help?

  5. What mistakes should I avoid?

I’m just trying to build something useful instead of guessing. Any feedback, criticism, or feature ideas are welcome.

Thanks for your feedback and comments in advance!

2 Likes
2

I like the idea of a demo suite like this. Mentioning QR codes, are you anticipating this running on mobile devices?

Hell yeah!

Ease of use, primarily-- something that makes it clear that things work well on this chain.

Swaps and cross-chain capabilities are my big things. Having more and decentralized methods of doing these are really important. Making them generally accessible sounds great.

Yes-- documentation and guides are a critical and often overlooked part of any project like this. It’s always important to consider them at conception.

I think a lot more concrete feedback will be possible once there’s something to either look at or play with (designs or demos.) Cool project!

2 Likes
3

Thanks for your feedback. Everyone is vocal on telegram and quiet on here :laughing: I don’t know how to cite your questions/comments, but I know how to copy and paste.

Mentioning QR codes, are you anticipating this running on mobile devices?

*When I did my first two computer test, I saw how painful it was to send in raw form. I have a special shorter import/export code that the app recognizes now. The QR code was mostly so you could use your phone+computer for the invite. I haven’t fully completed QR codes yet, but it’s in the works alongside YATs. I looked into the mobile path. Right now it needs walletd, backend, and frontend running on a PC. In the future if the tooling exists, I would love to make it local on mobile. It would require a lot of work though.

Ease of use, primarily-- something that makes it clear that things work well on this chain.

*100% agree. That is the main thing I’m trying to build toward first. Not just making flows technically possible, but making them clear enough that people can see what worked, what happened on Tari/Ootle, and what the next step is. I want the app to act like a guided demo/testing layer so someone can run it locally and actually understand the flow without needing to already know every wallet, indexer, and template detail. It does it through one main button now. There are currently swap, create, assets, progress, how it works, and advanced tabs.

Swaps and cross-chain capabilities are my big things. Having more and decentralized methods of doing these are really important. Making them generally accessible sounds great.

*I agree. Swaps and cross-chain are the bigger long-term goals. I’m trying to build the Tari native foundation first: clear local swap testing, easier two person flows, QR/invite sharing, and public test assets/NFT testing. Once that is solid and repeatable, cross-chain routes are the natural next step (BTC testnet is the first experiment, then EVM on my roadmap). I want it to be decentralized and user controlled, but also understandable enough that normal people can actually test, use it, and eventually trust it.

Yes-- documentation and guides are a critical and often overlooked part of any project like this. It’s always important to consider them at conception.

*I completely agree. I’m trying to treat docs as part of the product, not an afterthought. The goal is beginner friendly setup, screenshots, troubleshooting notes, and simple explanations of what is happening in each Tari/Ootle flow. If the app only works for people who already understand every wallet, template, or indexer detail, then it misses the point.

I think a lot more concrete feedback will be possible once there’s something to either look at or play with (designs or demos). Cool project!

*Thanks, I appreciate it a lot! You are the first and only response. Feedback will be much better once there’s something visual or playable for all. I’m enjoying playing around with it and learning. I’m going to keep cleaning up the local flow and work toward screenshots, a short demo, or a rough test version. Once that’s ready, I’d love feedback on what feels confusing, what feels useful, and what would make Tari/Ootle testing easier for more people. I still have a lot to polish up and add to it. With all the changes happening with it, I’m just testing locally with one or two computers for now and making changes each day. Once it’s working well, I’m down. I’ll consider dropping some teaser images at some point, so it’s not completely underground.

1 Like