Thread by @beemdvp

For my #NFT #DeFi #rustlang #scrypto challenge, I've created a #decentralized freelance platform! Here are my learnings from them all!🧵👇
github.com/radixdlt/scryp…

1. For authorization, its okay to use one badge for multiple components. You can think of authorization as a login to a service/platform you have in real life. Unless you have another whole service, just use one badge!

2. When creating protected methods, its also okay to use admin rights for components to store. This gives the flexibility that the component is able to call other component methods as well as an admin user (should you want to ofc)

3. A pattern I've been creating is you can relate an NFT to another NFT by storing the Non Fungible ID. For example, I have a unique NFT Contractor identity and I've picked up Work NFT, The Work NFT gets updated with the assigned contractor being the Contractor NFT ID

5. Testing #scrypto wasnt too bad an experience as I initially thought. The tricky parts were being able to understand how you can query the SubstateStore. It was tricky but you can use examples from resim to see how you can query specific resources/components/vaults

6. Try to keep in mind frontend requirements when you'd like to represent data. Its important to make your component eligible to be queried easily. This influences what you should store for users in a vault or what resources should be soulbound

Thats it, that's all I've got! If I've got your curiosity piqued and you're thinking what the hell is #scrypto? Its a #rustlang based #smartcontract language for #DeFi 👇👇👇
docs.radixdlt.com/main/scrypto/i…