Replies - Activity - salman.haider - Algorand

EncodeUint64 Error

Issue Reported

In the thread titled encodeUint64(asset_id) doesn't work, the user reports errors while trying to use the function. The user mentions they are using node version 14.17.0 and algosdk version 1.24.1. The user expresses that despite using the latest version, they still encounter the same error.

Request for Assistance

The user then requests help, asking, "please tell me if this solved your issue of storage? And how?" in relation to another topic, Overcoming the 64 key-value pair limit in global state.

Global State Storage Limit

Context of Query

In another post titled Global State Storage Limit of App in Algorand, the user questions whether the global states are exclusively stored in the app's storage and not in an account's storage. They also request examples and solutions for achieving this, as their attempts have not been successful.

Common Error: Overspend

Troubleshooting Advice

In a separate issue displayed in the thread Overspend error even though my account has algos, the user outlines their experience of encountering an overspend error while their account holds algos. They detail their configuration for connecting to the Algod mainnet API via the AlgoSDK scripts.

Seeking Documentation

The discussion emphasizes the need for documentation on deploying apps on the mainnet. The original poster mentions various errors faced during the deployment process, including requests for guidance on how to resolve these issues.

Function Calls in Smart Contracts

Challenges Faced

In the ongoing dialogue regarding Calling function of another contract in current contract, the user confronts a limitation on how many addresses can be passed in an accounts array and seeks methods for handling additional addresses.

Solutions Requested

The user also requests insight into managing smart contracts, particularly around operations like transferring tokens across contracts and handling returns of various operations while maintaining proper use of Algorand's capabilities.

Hash Creation and Error Handling

Addressing EcdsaRecover Issues

In another thread, issues surrounding Keccak256 Hash creation are discussed. The user specifies challenges when trying to pass signatures and hashes correctly, reporting errors with various attempted methods.

Concluding Remarks

The discussion emphasizes several technical challenges facing users implementing or troubleshooting Algorand's smart contract functionalities. Community members are encouraged to respond with solutions and clarifications about working examples and best practices regarding Algorand's SDK usage, smart contract development, and deployment procedures.