Replies - Activity - tsachi - Algorand
Contract-to-contract calls only possible between v6 contracts - not backwards compatible?
Mar 14, 2022
It’s required in order to ensure the callee would be designed to support being called by other contract. ( otherwise, there could be exceptions where this would defeat existing contract’s security attributes ).
What causes this error
Mar 12, 2022
Yes. A delayed transaction can cause that - but please note that were referring to a pretty long time here. I.e. in the order of hours. Alternatively, you might have your transaction being created by a node that wasn’t caught up… which explains the large rounds gap.
Algorand Catchpoints
Mar 8, 2022
The reasoning for the tree-directory structure under the “catchpoints” file is that on certain file systems, storing large number of files in a single directory makes the access time slower. This is not the case when you have several tens or hundreds of files, but it’s definitely the case when the …
No - it won’t expose your node in any way. The only way for you to “expose” is to have your relay listed as one of the SRV records. As long as that’s not the case, consider this to be your own private relay…
Admittedly, there is a way to catchup from an archival node. But you’ll need to do some tweaking: Configure the node as a relay by setting the NetAddress field. Once a catchpoint file is generated, you’ll be able to observe the catchpoint label in the “goal node status”.
Token Lock Examples
Mar 8, 2022
All correct beside the “reevaluate” portion - it’s never get reevaluated. The transaction content is being reevaluated - i.e. first valid/last valid / payer has enough money / receiver has more than min balance, etc, but the logic sig is evaluated exactly once. Depending on the implementation, some...
Sure. An incoming transaction ( regardless of the source ), would first go through a signature verification. Once it’s found to be a (potentially) valid transaction, it will be attempted to be placed on the transaction pool. When attempting to place it on the transaction pool, it would get evaluated...
Community driven verified tokens
Mar 8, 2022
The “shibainu test” refers to the promotional model of that coin ( per it’s own white paper ). The idea was to get a very large set of individuals ( i.e. army ) that would work on promoting the coin regardless of it’s functionality ( i.e. none ). I don’t know how many verified fake tokens are there…
Documentation on State Proofs
Mar 4, 2022
No, it’s not enabled yet on betanet. Betanet is supposed to be one step before testnet/mainnet, but enabling the feature there implies that the pipeline ( master - betanet - mainnet ) would be blocked until mainnet reached the desired participation key update threshold. Instead, it would remain dis…
The feature is not yet enabled. Before the feature would get enabled, the participation keys on the network need to be regenerated. I don’t know how long it would take… since it’s up to the node runners to renew their participation keys.
Limit of 10 Applications per account will change?
Mar 3, 2022
That was already implemented and it’s currently scheduled for the next release. It would likely to hit mainnet within a month.
Betanet with catchup
Mar 3, 2022
Could you please check what binary version you’re using, as well as operating system ? i.e. algod -v Also, do you have any participation keys on the node ?
Treat ALGO like an asset in the SDK to simplify a lot dApp development
Mar 2, 2022
The reason the SDK wasn’t implementing it as a single transaction is because of the underlying protocol. When implementing the SDKs, the primary goal was to clearly expose the core functionalities without introducing any higher level logic. Fabrice gave a good example with the asset sender here.
Archival Node Configuration - Behaviour of algod REST API
Mar 1, 2022
Once you switch the configuration from archival into a non-archival, the node would delete the old information on the subsequent restart. The archival/non-archival doesn’t directly change the way the REST API works...
global LatestTimestamp is 0 in when debugging from dryrun txn
Feb 26, 2022
@casper , yes I know that the tealdbg is a great tool for debugging. I just wanted to make sure you’re aware of other means to verify the correctness of your smart contract.
Query local state of a certain account from an application
Feb 24, 2022
The api you’re mentioning is currently under development is slated for the late March consensus release.
NFT drop :delayed release
Feb 24, 2022
I am unaware of a way to perform any type of delayed operations on the blockchain. You’d need some sort of an external agent that would send the transactions to “unlock” the content of the NFTs when time comes.
For security reason, it should not be possible to sign a transaction in a group individually
Feb 20, 2022
Yes, I agree that the signing software should give the end user to view all the transactions. In fact, it should highlight any request for signing of a transaction that contains the grouphash without showing and verifying the entire group.
Getting error while building node from source
Feb 16, 2022
Did you follow the README.md instructions ?
My Algo Wallet: Help
Feb 14, 2022
The mnemonics are the same regardless of the wallet you’re using. ( you’re correct in that they doesn’t have to be the same; however, all the Algorand wallets I’m aware of are )
Private network - node accessible from another VM within network or remotely?
Feb 11, 2022
Changing the EndpointAddress should make your node listen on the provided address. Please make sure to restart the node after making changes to the config.json file.
Algorand development challenges
Feb 8, 2022
Regarding the floating points support - The main issue with supporting floating points is that the hardware implementation for these tend to be non-deterministic. This limit the AVM from using these hardware instructions.