token

Token1 Contract

Token1 is a WASM-based simple token contract implementation that uses multiple Objects for storage, where each user has their own independent balance Object.

Implementation Features

1. Multiple Object Storage

   • Each user has an independent balance Object
   • Default Object stores token basic information
   • User balances are stored in their respective Objects

2. State Storage Structure

   • Basic information stored in default Object
   • Each user has an independent balance Object
   • Uses Object's native owner for ownership management

3. Security

   • Relies on Object's native owner mechanism
   • Users can only operate on their own balance Objects
   • Strict permission control (mint/burn limited to owner)

Main Functions

1. Initialize Contract

func InitializeToken(ctx core.Context, name string, symbol string, decimals uint8, totalSupply uint64) core.ObjectID

• Initializes token basic information
• Creates owner's balance Object
• Allocates initial supply to creator

2. Query Functions

func GetTokenInfo(ctx core.Context) (string, string, uint8, uint64)
func GetOwner(ctx core.Context) core.Address
func BalanceOf(ctx core.Context, owner core.Address) uint64

• Get token basic information
• Query contract owner
• Query account balance

3. Transfer Function

func Transfer(ctx core.Context, to core.Address, amount uint64) bool

• Creates recipient's balance Object (if not exists)
• Updates balances in sender and recipient Objects
• Includes balance checks and error handling

4. Minting Function

func Mint(ctx core.Context, to core.Address, amount uint64) bool

• Only callable by contract owner
• Increases total supply
• Mints new tokens to specified address

5. Burning Function

func Burn(ctx core.Context, amount uint64) bool

• Only callable by contract owner
• Decreases total supply
• Burns tokens from owner's account

Key Differences from Token2

1. Storage Method

   • Token1: Uses multiple Objects for state storage
   • Token2: Uses a single Object for all states

2. Ownership Management

   • Token1: Relies on Object's native owner
   • Token2: Uses custom owner field

3. Performance Characteristics

   • Token1: Supports parallel transfers (transfers between different users can execute in parallel)
   • Token2: All operations must execute serially (due to shared Object)

4. Functional Limitations

   • Token1: Cannot implement approve functionality (users cannot operate others' Objects)
   • Token2: Can implement approve functionality (all states in single Object)

5. State Access

   • Token1: Requires accessing multiple Objects
   • Token2: Only needs to access single Object

Usage Examples

// Initialize token
InitializeToken(ctx, "MyToken", "MTK", 18, 1000000)

// Query token information
name, symbol, decimals, totalSupply := GetTokenInfo(ctx)

// Query balance
balance := BalanceOf(ctx, userAddress)

// Transfer tokens
Transfer(ctx, recipientAddress, 100)

// Mint new tokens (owner only)
Mint(ctx, recipientAddress, 1000)

// Burn tokens (owner only)
Burn(ctx, 500)

Important Notes

1. Contract owner is managed through Object's native owner
2. New balance Objects are automatically created when receiving tokens
3. All operations include proper error handling and state rollback mechanisms
4. Contract events record all important operations
5. Transfers between different users can execute in parallel for better performance
6. Approve functionality cannot be implemented due to Object permission restrictions