Scrypto Types


In Scrypto, vaults are used to hold resources. Vaults are initiated with a resource definition and can only hold tokens of that particular resource definition. Here is how you instantiate a vault:


Buckets are a way to move resources throughout a transaction. At the end of a transactions, all buckets must be moved into a vault or burned. This is to make sure no tokens ever get lost between an account and a component.
You can take resources from a vault and put them in a bucket like this:
let bucket = vault.take(amount);
let bigger_bucket = vault.take_all();


BucketRefs are used when you write a method that could accept a bucket but you don't need to take ownership over that bucket. For example if you only need to get the quantity or resource definition of tokens inside the bucket you can define the method argument as BucketRef instead of Bucket. This makes sure that you will not be able to store the tokens in your vault or send them to another account.
Example of a method accepting a bucket_ref:
pub fn steal_tokens(&mut self, bucket: BucketRef) {
// No errors because we are only reading a value
info!("Amount shown: {}", bucket.amount());
// Error ! We are trying to take ownership over the BucketRef
You can see that we call bucket.drop() at the end of the method. It is required to drop the bucket refs that you receive or else you will get a ResourceCheckFailure when calling the method.


If you have the address of an account, you can instantiate an Account struct like this:
Account::from(address: Address)
Here is an example where we deposit a token inside an account:
pub fn send_gift(&self, address: Address) {
let account = Account::from(address);


Just like with an Account, you instantiate a component struct from the address of the component. You can then call methods on the component:
pub fn call_animal(&self, address: Address) {
let component = Component::from(address);<()>("make_sound", vec![]);
The type annotation we add on the method "::<()>" specifies the return type of the component's method. In this case, we expect it to return an empty tuple.

Import component with an ABI

Calling components like in the previous section is useful when you don't know the package's address at compile time. When you do know the package address, it is easier to use it by importing its Application Binary Interface (ABI). The ABI is a json representation of the package. It describes its functions, methods, arguments, etc... The resim CLI comes with a useful command to export the ABI of any packages easily. No need to manually write the ABI, try it with the HelloWorld package:
> resim export-abi [package_address] Hello
When you have the ABI and the package's address, you can import it inside your component:
use scrypto::prelude::*;
// Import a package at the provided address
// and with the provided ABI.
import! {
"package": "[package_address]",
"name": "TokenGiver",
"functions": [
"name": "new",
"inputs": [],
"output": {
"type": "Custom",
"name": "scrypto::core::Component",
"generics": []
"methods": [
"name": "free_token",
"mutability": "Immutable",
"inputs": [],
"output": {
"type": "Custom",
"name": "scrypto::resource::Bucket",
"generics": []
blueprint! {
struct ComponentCaller {
vault: Vault,
// You can now define variables with the name of the package as its type
free_token_component: TokenGiver
impl ComponentCaller {
pub fn new() -> Component {
Self {
vault: Vault::new(RADIX_TOKEN),
free_token_component: TokenGiver::new().into()
pub fn call_get_tokens(&mut self) {
// You can now call methods defined in the ABI
let bucket = self.free_token_component.free_token();