All - Activity - d13co - Algorand

Wallet error trying to send asset

From the message it seems like your (rekeyed wallet address) is no longer rekeyed to (my auth address). Check if this is the case on Pera, or look it up on an explorer to confirm its rekey status. E.g. Allo Info will show

Type [ Regular Account ] State [ Rekeyed ]

FYI rekeying “disappear…

Brief Randomness Beacon availability incident

The delicious irony is that the configuration change was part of changes that we are making for better observability and alerting for potential issues.

Earlier today we had a brief availability incident with the Randomness Beacon we run at the Algorand Foundation. The backend service submitting VRF proofs was unavailable for about 23 minutes. After that, the service was restarted and the proofs were caught up within 11 minutes.

Data here:

No synced node in Func

Can you try again? There was an issue with fast catchup that has been remediated. The Blocks section should now catch up properly.

Why expires timestamp is keep changing on node running on mainnet v4.0.1

Hi @AlgoUser1
The expiration time is actually specified in rounds (you can find your specific expiration round if you press ENTER in that screen). Since a “round” is not a meaningful unit of time for most humans, we try to estimate when this will happen based on the average round time of the last 1…

xGov 203: WARN..SCAM bot retroactive & txn fees (on-chain scam warnings)

Forgot to update this thread: the bot account has been funded 10,000 ALGO per the proposal. And users can now opt out of receiving WARN…SCAM transaction warnings here: https://warnscam.d13.co/

How the blocks are filling during the network stress?

The previous comment had incorrect calculations for max outer txn TPS, I think this is correct:

And in case it helps with your research, these are the largest blocks by transaction count at the moment:

rnd,txn_count
25836244,58888
25808869,51895
25836565,45323
25990224,44766
25990231,41958

You are welcome. You missed this part:

transfer the transaction files to your nodes
submit them with the goal cli (goal clerk rawsend)

Your code still submits each transaction individually over the HTTP API. Furthermore, I think it is doing so sequentially. While you have some multiprocess “plu…

[xGov][Community meeting][New Version][2024/04/04]

Re: non-linear voting power @pescennius @CryptoFarmer: If there is any voting power benefit to splitting up your stake to multiple addresses (“sybils”), this will be exploited. The xGov voting power system can not be vulnerable like that, and I am not aware of any solutions to this problem that do n…

Reject from smart contract with pre-defined error message?

Bumping this to say we did use the custom asserts, and they were very useful in (eventually) figuring out that a subset of nodes that some users were using were out of sync - not sure we would have been able to deduce that otherwise. The contract, including the custom_assert gadgets, are open-sourc…

Feedback request on proposed Q4 2022 governance measures

AlgoFi supports the keyreg transactions. Where you run your participation node is up to you. So you can participate via a vault and keep your existing node on 2023. That said, participation nodes should get a gov boost of their own.

Analytics monitor: Voting by commitment size: 10M+ wallets carrying 1B so far

We made a website showing Governance Period 4 votes by commitment stake: https://voting.algorand.observer/ This updates every 10 minutes and feeds off the Foundation CSV feed. An interesting trend surfaces: The 10M+ “whale” governor group carries the B vote in Measure 1 entirely by themselves.

Governance Period 4 Voting power centralization, consensus participation and known entities

They seem to recognize that passive gov rewards need to be reduced/redirected to more productive incentives that will lead to on chain economy (and TVL and token price) growth. Others may have different issues but to me this is actually the highest priority, and if we exit the bear market with incen…

Happy Birthday, Algorand!

Happy Birthday, Algorand! Algorand is celebrating 3 years since the genesis block - also known as a birthday! Block zero was at 2019-06-11 00:00:00 UTC.

Is the 1000 block retention configurable in algod?

From here: Non-Archival nodes will delete old blocks and only retain what’s needed to properly validate blockchain messages (currently the last 1000 blocks). Is this configurable? I’d like to be able to query my algod from blocks 18M onwards. My idea was to give it a catch to a ~18M catchpoint and…