Yulong Wu

Just wanted to add that trait support is still on our backlog. We should be able to contribute to this thread more once we start working on it.

This is not immediately required as Scrypto is evolving fast.

This requires some thinking. It really depends on how we treat `Account` in the future, either as a trait or a specific type. With the "trait" approach, we will be...

This also affect `with_static_info` scheme, where type info is stripped for performance in collection types.

Only the verbose option should work. ``` // works (assuming the tx includes a DropAllBucketRefs instruction) pub fn show(&self, amount: Decimal) -> BucketRef { self.sample_vault.take(amount).present() } ``` ^ This smells...

> works, but very verbose, would much rather just use "show()"...but... This is essentially how `authorize()` works.

Thank you @devmannic for the suggestion! I understand that there might be some use cases which require direct access to the blueprint struct, but I'm not feeling comfortable exposing it...

Thank you @kroggen for making the suggestion. I'm not able to look into this immediately, but will keep the ticket open for further investigation.

Hi @dRAT3, thanks for raising this up. I'm hesitating to provide documentation about `SmartValue` at this comment, as it will likely be replaced with `sbor::Value`. For now, you can consider...

As of now, both badges and tokens are backed by resource. The only difference is granularity: - Tokens have granularity of 1 (which is `10^-18`) - Badges have granularity of...