Thread by @jacobmtucker

A huge update is coming to #Cadence, the smart contract language used by @flow_blockchain:

📥Attachments

What are they and how do we code them?
👇🧵

@flow_blockchain 📽️Before I begin, I made a YouTube video diving into attachments here:

@flow_blockchain 1/ What are they?

Attachments are what they sound like: things we can attach to resources and structs in Cadence.

⚔️For example, we can attach a "Pet" or a "Weapon" to any NFT.

@flow_blockchain 2/ Composability

This is insanely cool if you think about it. It represents composability at its finest.

📦You can define your own attachment and place it on *any* resource (like an NFT) that you own. You are literally building on top of pre-defined assets.

@flow_blockchain 3/ How to define them?

In this case, we create an attachment called "Pet" that can be attached to any `NonFungibleToken.NFT` type on @flow_blockchain.

@flow_blockchain 4/ How to attach them?

Simply use the `attach` keyword to add an attachment to a type that it can be attached to.

@flow_blockchain 5/ How to access an attachment?

We can use bracket notation `[]` to access an attachment on a type.

@flow_blockchain 6/ Learn More

Read up on attachments here: github.com/onflow/flips/b…

Watch a video on it here:

@flow_blockchain 7/ Conclusion

Thanks to @C_3PFLO for making a super cool demo here: github.com/C-3PFLO/flow-r…

You inspired me to make this thread! ;)

Follow me for more Cadence tips 🥳