All - Activity - nullun - Algorand
Staking 2ALGO not PAID-HELP
If your account isn’t already marked as eligible and you would like to become eligible, then yes you will need to submit a keyreg transaction with the fee set to 2 Algo. You can simply submit a new keyreg transaction with the same participation key details as before (assuming they’re still valid).
How to invite some to this forum
I’m not sure what you mean by invite. You can just send them the link and have them sign up like you did.
Any node service provider for Algorand?
There is also https://algod.algorand.chain.love/v2/status.
HashiCorp Vault for Algorand key signing
I don’t personally have experience on this, but have you checked out the Hashi repo from Algorand Foundation? It may be able to do what you’re attempting.
Replace-By-Fee transactions
On Algorand there isn’t really a concept of a transaction "getting stuck". The transaction will either be accepted by the node and propagated through the network, being included in the next block, or it will immediately fail. In the event the network is so congested that the backlog queue for that node is too large, then it may simply be that the transaction is taking longer than expected to be properly processed.
Where is my algorand? please help me!
If you’re looking at your address on an explorer and the funds you expect to see are still there, then you can be sure they’re still in your possession. You may want to check the status of the hardware wallet you’re using to see if they’re experiencing any issues displaying account information.
Problem transferring Rio (Realio) from Pera to Rio wallet
Accounts on Algorand may only receive assets they’ve chosen to receive. This is done by “opting in” to receive them. On the new account, in the wallet you’re using, you need to find where to add an asset, or opt in to an asset. Once you’ve done that, then you can receive it from your other account.
Goal clerk rawsend: HTTP 400 Bad Request
You should have created a complete new thread for your own issue, rather than comment on a 2 year old completely unrelated thread. The account N44XKK has been rekeyed to GW7IF6. This means the private key (mnemonic) for N44XKK is no longer used to sign transactions for that account. If you wish to manage this account, you need to use the new key.
Minimum Balance and Wallet management
Yes, this is correct. The MBR will be recalculated when creating or resizing a box. For smart contract I’ve written, I will make my ABI method require a payment transaction as one of the first arguments, and check the payment contains the correct amount. Then when deleting a box the MBR is recalculated.
Algo deposit problem from Binance to Coinlist
The transaction is confirmed on the chain, so it’s there. You’ll need to speak with Coinlist to find out why they’re not crediting your account.
Sending USDC ALGO to an USDT ALGO address
Right, OK, so you’re talking about depositing assets into Binance. It looks as though the address is the same for both USDC and USDT. However if you’ve not been credited for it you will need to contact Binance support. The transaction is final and now Binance owns the account which holds it.
ASA verification 1245322723
I’m afraid Algorand don’t have any control over AlgoExplorer, I’d recommend reaching out to them directly here.
Sending USDC ALGO to an USDT ALGO address
Welcome to the forum. Could you share some transaction IDs to help me understand what you mean? What you’re saying doesn’t quite make sense to me. If an account isn’t opted in to USDC then trying to send USDC to that account would result in the transaction failing and the USDC remaining in the original account.
Can a block be created in less than 3 seconds?
There isn’t really any way to know the exact time. Since the blocks will always take some amount of time to propagate across the network, and each proposer may be from anywhere. So you can only really time the duration between blocks that your own node receives. Maybe if you setup multiple nodes all around the world and compare timings, you may find instances where blocks are created incredibly fast.
Outgoing Transaction Always Failed Without Auth Address
Unfortunately not, if an account has been rekeyed then only the new auth-addr can sign transactions for it. Check all the different wallets you’ve used.
Does exist a limit for block payload size?
The error you’ve shared talks about access budget for boxes. Essentially each box reference you include with the application transaction provides up to 1K of write budget. With budget pooling you can include the same reference multiple times to increase the budget. So if you were to include the same box reference in your application call, you might have better chances with your transaction.
Is it possible to transfer smart-contract (dApp) ownership?
When an account deploys a smart contract, the approval/clearstate, and any global state data is stored against the creator's account. Similar to how assets/NFTs are stored on their creator account. The ownership cannot be transferred, and the minimum balance requirement will always be on the creator.
Delegate fee to another account
Yes, the transactions must be part of the same atomic group. However, the transaction that’s paying the increased fees to cover the whole group can be any transaction they like. I’ve previously made the “fee covering” transaction a payment transaction that sends 0 Algo to itself but with double the fees.
Reject from smart contract with pre-defined error message?
Lol, I appreciate the kind words in your tweet. This is a smart solution, and if you can afford the additional opcode budget and it benefits you then you should definitely use it. Since you brought this up I had been meaning to create a minimal demo that parses the error and reads the PC, etc.