TROVE
@TroveEco
Followers
1K
Following
1K
Statuses
221
Secure and simple tools to swap digital assets on #Radix 🔃
Babylon
Joined May 2023
There is an immense opportunity to develop the future of NFTs on Radix - truly innovative and leading web3 digital assets. Trove aims to be at the forefront of this. Couldn't be in better company than with @surge_trade in the push for creating trading experiences that will turn heads. Thank you @radixdlt
Kicking off the Radix Foundry initiative, the first two grant recipients have been announced: @surge_trade ⚡ and @TroveEco 🎨 Discover what both projects are building as part of the Radix Foundry 👇
9
14
59
RT @timanrebel: Really excited about the new Trove Pro 🤩 Full-fletched NFT Marketplace coming to @radixdlt And of course, I made a Taylor…
0
33
0
Sorry to hear that cocopuss - but understand it! Trove as you see it today is a dapp made a year ago intended just for p2p swaps and was meant to be a small utility dapp, not the main marketplace for Radix NFT enthusiasts. It's not been worth putting hours into that app as the demand is for a more conventional NFT Marketplace - which is why all my time is focused on getting Trove Pro out the door, an advanced real-time marketplace with all the fixings you'd expect from an NFT marketplace typically. Trickling updates out as I can on @ripsource. Updates for Stokenet testing coming soon.
1
1
5
RT @KonstantinKoos: 10.000.000 TPS (transactions per second) is even possible? Apparently it is on #Radix - and @fuserleer just did a stab…
0
213
0
RT @PiersRidyard: Not long before I touch down in Singapore 🇸🇬 for #TOKEN2049 with the rest of the squad @radixdlt @CaviarNine @radixchar…
0
17
0
Right now its: Take asset A out of an account, place it in a component with some listed price, someone else deposits the right amount into the component and they're able to retrieve asset A. So each marketplaces' components essentially lock up the asset and have embedded fees that make any aggregation a bit pointless + fragments communities & liquidity. The current P2P swaps platform, that is Trove, essentially does this but doesn't have limitations on what you put in the component (i.e. 20 different NFTs with 20 other tokens, asking for 20 other NFTs and 20 other tokens in return). However, its primarily used as a typical NFT marketplace atm. The new version of Trove I'm working on will move to this more open/kiosk-esque style approach as a more dedicated marketplace - along with opening up for a lot more types of marketplaces to pop up hopefully. There's another marketplace coming along called Foton, which is making some awesome creator tools and has built out a nice mechanism for royalties to work within their platform too.
0
0
7
@wyliepieote @radixdlt you've seen my console logs too wylie, so you know I didn't just make this
1
0
1
@aus877 @KamalaHarris stop caring about politics and your country, you're ruining my attempts to purge my algo 😁
1
0
2
Depends what your smart contracts are for, some will be better suited than others for dev royalties. Also depends whether your open source or not. I mentioned on my other comment in this thread about versioning and that's probably an important part to opening up dev royalties for more broader use-cases when open sourcing. If you're not open source though, decompiling a Scrypto blueprint from wasm is not a super obvious task atm, and not a lot of devs know how to do this - there's a tipping point where that expertise/process is worth it, but otherwise just paying for a small fee on a component someone else has monetised is probably worth it - especially if you're building quick/prototyping/testing if there's a viable model. There are some small utilities I just don't want to have to build from scratch myself. This might be something like a Random Number Generator, escrow systems, a control accessor for badges/multisig, a custom data store, etc. All on their own are nice small manageable projects, but when I'm thinking about the totality of a dApp which may be 10 - 12 blueprints already... it would be nice to know I don't have to start from scratch and there's someone actively keeping their utility up to date/adding functionality. Another aspect that doesn't get much light is the regulation aspect, depending on your jurisdiction/varying local regulation, the dev royalty model could be quite attractive.
0
0
7
^ Trove uses this developer royalties module on its smart contacts and it's worked pretty nicely for the past year. Set up a blueprint and receive royalties on every sc instantiated from it. Encourages some interesting fee models that are atypical to other networks. Next upgrade I'm working on at the moment transitions to a completely open source model (current setup is semi-private) and developer royalties will play a key part. Looking forward to versioning capabilities too which I think will really offer a viable OSS monetisation opportunity.
0
2
17