r/algorand • • Oct 20 '21

Faucet Coming to an End

1.5k Upvotes

It's with a heavy heart that I have made the decision to shut down the faucet. While generally I've been able to keep it around a smallish loss each month, I no longer have the time to put into it that it deserves in order to add functionality and options for increasing the Algorand available to give out to be able to handle the increasing popularity and number of requests every day.

I'm going to let it run until the end of the current month, but will shut it down after that point.

I do want to say, that this community has been so supportive and I've been very happy to see the community and usage of Algorand grow over the last year. Hopefully the faucet had a small part in that growth. Thank you to everyone for all of the kind words and all of the support this year. I wish you all the best in your Algorand and Crypto journey's!

Thank you to everyone in this community again!


r/algorand • • Sep 08 '21

What's going on? šŸ˜‚

Post image
1.1k Upvotes

r/algorand • • Sep 08 '21

JUST BROKE $2!!!

Post image
988 Upvotes

r/algorand • • Oct 14 '21

Governance Celebration GIVEAWAY! 3 WINNERS! 100 ALGO, $50 OPUL, $50 YLDY

854 Upvotes

Happy Governance! To celebrate the start of governance and everything heating up in the Algorand ecosystem #AlgorandAutumn, I'm hosting a giveaway!

To enter, comment a number 1 - 100,000 and the closest guess wins

Enter by 11:59 PM ET today, 10/14

You don't need a wallet to enter. Multiple entries will be disqualified. In case of a tie, the older comment will receive the prize

To clarify, one winner will receive 100 Algos, another will receive $50 worth of OPUL, and another will get $50 worth of YLDY

I'm committing to winners verified inside this hash:

dd92a03c1c9750128b8351e4ab25a7baf6a450d22fa86675df62a969dceb0a3b

Edit: thanks for all the entries and support just don't forget to upvote the post to increase visibility!

Edit: figuring out who won after I finish all my work lol. Prob announced relatively soon and will message the winners

Edit: congratulations to u/tyschab u/Algrainga and u/jsr33 for winning! I'll message you all.

The has was a sha-256 of

Love manbearpigxxx 45916 ALGO 33328 Yieldly 89097 OPUL


r/algorand • • Nov 02 '21

Algorand founder proposes new use case for Algorand blockchain inspired by Elon Musk’s reply to WFP director.

Thumbnail
gallery
800 Upvotes

r/algorand • • Oct 04 '21

Algorand ads at the Bruins game

Post image
791 Upvotes

r/algorand • • May 19 '21

Where’s my ALGO HODLers at?

Post image
704 Upvotes

r/algorand • • Sep 18 '24 Heart of Silver

Price Upvote if you believe $ALGO will reach and surpass $1 šŸš€

Post image
697 Upvotes

r/algorand • • Nov 18 '21

General Wtf?

Post image
687 Upvotes

r/algorand • • Aug 11 '21

Algorand Misconceptions

683 Upvotes

Hi all,

The purpose of this post is to attempt to clear up some common misconceptions regarding Algorand. I’m not going to go into why I believe Algorand is a sleeping giant as there are plenty of resources that cover off Pure Proof of Stake and the benefits this design brings to the blockchain world. That said, there are a number of prevailing misconceptions that lead to a fairly common and erroneous understanding of how Algorand works. I don’t claim to understand Algorand perfectly, and these points are purposefully high level as a detailed explainer wouldn't fit one point let alone all 3!

Disclaimer - obviously a substantial amount of my crypto portfolio is in ALGO.

Also, thank you to u/BananaLlamaNuts, u/Unlucky_Life_479, u/AsoganM1977, u/bitter_byte, u/Algo_staker, and u/RobbeeSan whose own posts elsewhere helped me to understand and compile this :)

TL;DR

Algorand has a long term vision seeking genuine, institutional level, mass adoption. Consequently, Algorand has been designed to achieve this goal even if its chosen methods may be at odds with what is the generally accepted way to do things in the crypto community. Issues relating to tokenomics and centralization are misunderstood mechanics that in theory actually serve to increase Algorand’s chances of succeeding.

Issue #1 - Tokenomics

It’s complicated. More so than any crypto I’ve ever invested in before. Algorand’s perceived subdued price action (at least in comparison to other popular projects) can appear to be by design but in truth, the mechanics causing this tweaks volatility at best. Algorand’s tokenomics have two triggers in this regard:

  • Accelerated vesting/release of additional ALGO that occurs when the 30 day moving average hits a new all time high. This has not happened since April. Importantly, this will cease in 2023 (unless a governance decision alters that which is never off the table).

  • Continuous distribution of early relay node operator rewards increases the supply of ALGO into the ecosystem for stability. This does act as a deflationary mechanism however the hard cap on total ALGO has not changed. Contrary to the odd belief that people with big stakes would want to see their investment reduce in value (as this was a known mechanism when they signed up) this acts as an incentive to grow the network and it’s value.

The perception that Algorand’s tokenomics are bad undoubtedly stems from the poorly received ICO (which used a Dutch auction and isn’t exactly in the spirit of decentralization) and the impact the above mechanics had when used as originally planned. Unfortunately the ICO was seen to be murky at best, and the mechanics intended to reduce volatility were too effective. The price tanked. Algorand cancelled a second planned auction and went back to the board and tweaked the system to be what it is today.

But why go to all this trouble? Algorand is pitching it’s capabilities to banks, governments, and wall street. To be effective in achieving its goals Algorand must demonstrate general professionalism in what is perceived to be a very unprofessional space. Algorand works hard to stay away from both the FUD and hype, instead focusing on securing their ISDA and trying to demonstrate a stable product in stark contrast to the volatility that is a lot of the crypto space. In this context reduced volatility is a strength, not a weakness. This sets Algorand apart.

Algorand is not seeking instant success. It’s seeking mass adoption and this approach, while different and generally seen as ā€œbadā€ in this community, is considered a key enabler in making that happen. If you genuinely want to consider the positives regarding Algorand’s tokenomics, it’s that time is on the side of small-scale investors to accumulate as much as possible at a reasonable price before scarcity enters the frame. All of the pieces are in place, dApps are coming, and Algorand’s ecosystem is set to explode.

Would you like to know more?

EDIT 7th September 2021: This post over on the official sub is a very good read about one aspect of the tokenomics.

Issue #2 - Technical centralization

From a technical standpoint Algorand is more centralized than blockchain purists would like, and yet it is actually nowhere near centralized. The decentralization, security, and scalability properties of Algorand will improve as the network matures, so the centralization argument is more about Algorand’s youth than its design. That said, understanding Algorand’s design may help you see that things are not as bad as they might appear if you only ever get your technical information from certain parts of Reddit.

There are two types of nodes on the Algorand network; relay and participation, and to conflate them is to misunderstand how Algorand works:

  • Relay nodes form the communication network and are responsible for the high transaction throughput that Algorand is capable of. Relay nodes do not perform consensus but do enable the participation nodes to remain disconnected and less vulnerable to attack. Relay nodes are needed to add blocks but cannot affect the integrity of block composition or the chain. If every single relay node turned malicious, the impact would be to stall transactions on the network until an honest relay is re-established. Relay nodes cannot destroy the integrity of the blockchain.

  • Participation nodes provide the actual consensus by creating, validating, and certifying blocks.

Like most blockchains, increasing the number of nodes improves the decentralization, scalability, and security of the network. Anyone can run a relay or participation node, but will not be rewarded for doing so (for now). Required specifications to run a relay node are quite steep, particularly on the network side, so most people opt to run a participation node which can be run on something as simple as a Raspberry Pi and 0.1 ALGO.

The talk about centralization stems from the fact that at this point in time relay nodes are only really being run by 100 early investors, commercial entities and non-profits (Universities). In the context of existing mainstream systems, 100 independent operators is very decentralized, but in the crypto context it may as well be a single computer.

Algorand’s design also allows decentralization to be easily expanded and improved, but once the ecosystem is mature enough and not before. This is wholly aligned with the slow and steady approach touched on in issue #1. The Algorand network is approaching this transition point, but may still be a year or more out.

Lastly, when decentralized governance kicks in later this year it will, in theory, eventually decide the relay node white list / the need for a white list / the incentives for running a relay node. So as Algorand matures all holders will be given the opportunity to vote on how this is handled, not just the existing relay node operators.

Would you like to know more?

Issue #3 - Governance centralization

While technical centralization is a misnomer, governance centralization is unfortunately a little more accurate but once again isn’t as bad as first impressions may indicate even when compared to its peers. Decentralized governance is coming, starting Q4 of this calendar year as a hybrid between the current automated staking system in parallel with governance rewards. This will then switch entirely to governance only rewards starting Q1, 2022.

The problem Algorand has is that early founders secured themselves a golden ticket by being preselected to run relay nodes, with huge initial funding and ongoing super staking rewards. They earn huge fees for running relay nodes, which compounds their stake, giving them an even more disproportionate amount of control over governance. These early relay operators will end up with +30% of all Algos in existence, assuming they don’t sell.

This issue leads us back to the perception of centralization in that a small group is occupying most of the decision making power. In general, the main value proposition of blockchain is that it’s meant to be trust-less without relying on an institution to be honest. The forthcoming governance model will be a one-algo-one-vote situation, so those early adopters will have the lion's share of votes going forward. So even with governance moving on-chain, Algorand may still have a centralization problem.

However, as with everything in this not-at-all-biased explainer, I’d happily compare Algorand with its peers. In reality some of the more established and successful projects (if price was the sole measure of success) with their large mining pools have a far more concentrated balance of power than Algorand. Additionally, a bigger stake equals more to lose so larger actors in the Algorand ecosystem should act in the best interest of the network. They logically want to protect and grow the value of their investment and I for one am happy to let them have their say because one ALGO is the same no matter who holds it. If they do something to increase the value proposition of the network, and in turn the value of ALGO, then it is literally a win for all holders.

Would you like to know more?

My Personal Opinion

Algorand is going after big business and doing it in a way that is more aligned with what big business would traditionally expect. This is at odds with crypto ideals and undoubtedly where the skepticism regarding Algorand comes from. Teething issues at ICO exacerbated the problem. This doesn't make Algorand a bad investment and those early issues are now thankfully behind us. Of course time will tell if things work out as intended, but this is no different to literally every other project in the cryptosphere. Algorand is in my humble opinion one of the most solid investments you can make in this space.

That's all I have (for now). Thank you for reading. Have a lovely day :)


r/algorand • • Jun 09 '21

Me this morning

Post image
677 Upvotes

r/algorand • • Jan 17 '22

Meme I "attacked" Algorand's network (testnet)

661 Upvotes

Ok, so I saw a few posts asking how Algorand would react to a huge influx of transactions a week or so ago, like what happened to Solana and Polygon which had some issues under pressure. Solana slowing down to a crawl and Polygon going over 100x with their tx fee. Dunno if HarmonyOne's 24h shutdown was because of network congestion, that one's pretty recent.

So anyways I decided to "attack" the testnet network for an hour or so, seemed like the only sensible thing to do, nothing much going on at work right now anyways.

Ā 

This is my methodology :

I started by wasting around an hour getting 4300+ Algos from dispensers. I can now distinguish between regular pictures and captcha images, I can fairly confidently say I'm not a robot.

I calculated how many transactions would fit in an hour's worth of blocks. The answer is 3 600 000. 1000 Tx/s x 3600s in an hour = 3 600 000 tx.

I then pre-made my 3 600 000 transactions to try and send them all at once in 6 groups of 600 000 tx. It took like 60 hours to prepare and I hit a few problems already.

  1. It seems like all transactions on the Algorand network have a 1000 blocks lifetime which I didn't know about. If you make your transaction at block 1 000 000, it NEEDS to be pushed to the network before block 1 001 000, otherwise it gives a transaction validity error. So my first batches of 6x 600 000 transactions were wasted. Fun!

  2. There was also an issue with concatenating 600 000 transactions at once, I had to do a "find" operation first, then concatenate through xargs cause there were too many arguments for cat to work properly. That's a limitation on cat, nothing to do with algorand.

  3. I wasn't able to sign the group transaction holding 600 000 transactions. It would always time out with an error message : "couldn't sign tx with kmd: handle expired". It might be interesting to try to sign with more than 2 vCPUs to see if it would work.

  4. On my first actual "attack" try (starting on block 19 160 900), I also found out about network congestion. Basically wasted another ~3 600 000 tx! So to get priority transactions, I put 1200 micro Algos as fees for my second "attack". The message I was getting was this : "Warning: Couldn't broadcast tx with algod: HTTP 400 Bad Request: TransactionPool.Remember: fee {1000} below threshold 1076 (4 per bytes * 268 bytes)"

  5. On my second try, starting on block 19181000, the network congestion went from 4 microAlgos to 8 microAlgos per byte.

So I already learned a few things.

  • I learned to make smaller grouped transactions. I created 360 transactions group of 10 000 transactions for easier concatenating and signing. In retrospect I should have went for 4600-4700 tx in a group to be as close as possible to a block. I'm ready for the 10K TPS upgrade I guess...

  • I needed to know when I wanted the "attack" to begin and calculate the starting block, thankfully we can pre-create transactions with a future valid starting block. Knowing that 1000 blocks is around 1h15m, my test would work within the transaction lifetime so I didn't have to do multiple batches with different starting blocks, which is great cause it would have been a pain. I gave myself a target block to start the first test of 19 160 900 and 19181000 for the second one. It would also work out for the tests to happen on a weekend, which is great cause even though I don't have much going on at work right now, I still have some stuff to do. On an 8vCPU VM and with 4 scripts building transactions, it took around 10 hours to make those 3 600 000 tx.

Ā 

I made 360x 10 000 signed tx files. I found out that if you try and send them all at once, only around 20 000 transactions get sent at most, even before network congestion, I'm guessing that's the max size of the mempool or something? I tried with 35K in one batch and only about 20K went through. But I also noticed I could spam them again and again and eventually they all go through. Let's say tx1 works but tx2000 is skipped in a group, if I send the whole 35K tx again, it'll skip tx1 this time since it's already on the ledger but do tx2000.

So anyways I created another script to keep trying to send those transactions for the forseeable future. There's 2 loops, an initial one where I wait 2 seconds between each group to let my VM catch up. The second script I just send everything at once and whatever's not on the ledger yet should get pushed.

Ā 

Some general notes :

  • I very quickly got to the network congestion. Within 5 blocks. Meaning my threshold for transaction fees should have been closer to 1076 instead of the standard 1000 to at least be valid on the network. That's why I put 1200 microAlgos as fees on my second test, I wanted to see if I could get over everybody else. It worked for a while but I still hit network congestion within 5 blocks again.

  • I also found out that network congestion has multiple levels. It can push the fees even higher at 8 microAlgos per byte. So the fees can go closer to 2000 microAlgos for standard transactions, most likely even more.

  • I changed the sleep command from 4-10 seconds in my "attack" script, the network congestion really screwed me over. I left it at 8 seconds from block 19 181 320 onwards to put as much pressure as possible on the network and push people out of blocks. It seemed to be the sweet spot. Next "attack" I'll make 4675 tx groups, which is about the max size of a block during congestion, and push one group transaction every 4.3 seconds to be at the exact sweet spot between network congestion and full TPS.

  • The biggest blocks were 4697 tx

  • When the network congestion happened, there was a loop going on. Transactions accepted for 3-5 blocks, transactions ignored for 1-2 blocks, transactions accepted for 3-5 blocks, etc. The issue was the size of my transaction groups. 10K tx fit in around 3 blocks. "Attacks" like these need to have grouped transactions be as close as possible to the block size.

  • It took around 10 hours to build the 3 600 000 transactions for an hour's worth of "attack" on a 8vCPU VM, so already there's a bottleneck for an "attack" on mainnet in real time. Obviously there are faster ways to build transactions than what I did. It could be done with more parallel processes, create 3600 batches instead of 360. It could be done with a much faster CPU. Or it could be done on multiple nodes which is the most likely better option. I'd say maybe 50 nodes making 100 transactions per block should be fast enough to work in real time instead of having to create the transactions "en masse" before the "attack". You could just run a simple loop for this. I can imagine a 5 host ESXi/proxmox cluster with 10 VMs with 2vCPUs on each host. Could be done with a bunch of cheap servers for a total of maybe around 3000$ of hardware + the transaction fees and you could have a real time "attack" on Algorand.

  • Each signed group transaction of 10k transactions was about 2.6 MB for close to 1 GB total.

  • The block tx speed went from a stable 4.2 seconds to 4.4 seconds per block during the "attack" according to https://testnet.algoexplorer.io

  • I filled about 3 out of 5 blocks between 19181000 and 19182000.

  • I wasn't able to send all my transactions before the tx lifetime ran out. I was able to send for 3108 Algos worth at 0.0012 Algo a transaction so only about ~2 590 000 transactions out of the 3 600 000 made. Lost 28% of my built transactions because of network congestion. Again though, it seems like having better tx groups would have helped here.

  • For this test, I did it from one machine, one node, one public Algo address, one public IP. I would like to try this from multiple IPs/nodes all over the world and multiple Algo addresses and coordinate the whole thing. I can spin up around 10-15 droplets on digital ocean whenever I have time and try this again to see if a coordinated "tx attack" could affect the blockchain in some other unforseen way. I'd really like some help from a testnet faucet or from the community for this, I'm honestly tired of answering captchas... If anybody wants to help my next shenanigans, I'd love some testnet Algos sent to GTGIWTMQDFFZETS3ILBHTEQ36KH5HTJBUIRZX6UZ2X7PDHYF2VXREMTWTA. You can ask for some at https://bank.testnet.algorand.network.

  • I'd also like to do an "attack" with notes having close to 1kb of data at one point, see how the indexer nodes react. Transaction fees are gonna be huge though, especially if there's congestion.

  • Ideally I'd love to do this test on mainnet, but I don't have 4000+ Algos to spare for that kind of stuff. If the Algorand foundation or any other entity wants to help with this, I'd be happy to display how strong the network can be and write in details everything that was done to prepare and do the "transaction attack".

  • Now that the 10K TPS upgrade has been scheduled for Q1-Q2 2022, I've got the exact scripts to do the "attack" with 10K tx per group.

  • To go over me during the "attack", people would have to check what kind of level of congestion we're at. It could be 4microAlgos per byte, or 8microAlgos per byte which I've seen so far, dunno if it can go higher than that. At 8 microAlgo per byte, it would have cost me 0.002 Algos per transaction, pushing it to a whopping 0.003$ USD per transaction, still a lot less than a penny. It's not much for a bunch of users, but for a sustained "attack" it could raise the price to 2 Algo per second, or 7 200 Algo per hour or ~10 000 USD per hour. Not sustainable. And it might go higher than that depending on the congestion.

  • I might have blocked off a bunch of valid transactions for the hour because of this congestion, I'm sorry for anybody testing and wondering what the hell was happening, the blockchain was working as intended! The biggest issue I see is it didn't automatically set the fees to the right amount because there were actually a few blocks at zero tx, which sounds highly unlikely. The "background noise" for the testnet network is 5-10 tx per block. https://testnet.algoexplorer.io/block/19181054, https://testnet.algoexplorer.io/block/19181162 , https://testnet.algoexplorer.io/block/19181340 and https://testnet.algoexplorer.io/block/19181634 for instance. Right after full blocks.

  • It feels like there should be a way to see the current "congestion fee" from the goal CLI to create and sign before sending. I tried to send regular transactions and the fee was set to the default 1000 instead of the actual required fee of ~2000 with congestion and they failed. This feels like the biggest problem to me so far. If you have an automated script sending transactions and it just happens to be during peak congestion, they would simply fail. There doesn't seem to be an automated way to send a transaction with whatever the current congestion fee is. People on other dApps would be have to try transactions a few times before they would be valid at 1000 microAlgos and sent to the network. Most of the dApps/games would work maybe ~80% of the time. The blockchain itself would be fine, which is really good, but the user experience on dApps would be bad because most transactions wouldn't post to the network. View Edit2

  • And finally, the last part of this whole thing : It was mostly a waste of time, the network worked for the whole hour of the "attack". No slowdown, no exhorbitant fees, no downtime. I did block a few people from pushing transactions to the network because of congestion fees, which is an issue Algorand inc should look into. these people should figure out when making/signing their transactions. There's a way to adapt dynamically. GG I guess.

Ā 

If you have any notes on how to test the network in another way, let me know and I'll try to find some time to test it!

Ā 

TLDR : I flooded the testnet network with a bunch of transaction for an hour and it didn't die. My test isn't perfect (because of the size of my grouped transactions which I didn't think through), but it's still a pretty good display.

Ā 

EDIT. Removed the scripts to not incentivize or normalize these kinds of tests on testnet.

EDIT2. Oh well, the only criticism I had has been answered below by logiotek. Thanks a lot!

Algod API has a method TransactionParams() which pre-fills transaction with parameters relevant to current state of the network (including current minTxFee) and should be called as a starting point when building any transaction. There is also a method SuggestedFee() which can be used to update a fee of a previously composed transaction with fee that matches current network state (useful when retrying sending transactions that were not previously accepted). Anyone that's not using these methods as it was intended will be censored during congestion.


r/algorand • • May 02 '22

News FIFA have announced an agreement with Algorand in which they will become the official blockchain platform of FIFA

Thumbnail
twitter.com
585 Upvotes

r/algorand • • Jun 01 '21

Royale presents: "I LOVE ALGO" Tournament - 50 ALGO up for grabs!

583 Upvotes

Hello Algonauts!

Not sure if y'all have heard of Royale. It's a browser-based Battle Royale game that runs 24/7, offering Crypto to its survivors. We've had a lot of people join our discord asking if we can get some ALGO into the action, so it is our Crypto-Of-The-Week. This coming Sunday, we'll be showing the Algorand community some love with a tourney that dishes out 50 ALGO! If you're interested, hop on to our discord server and sign up! Details below:

Time and Place:

Sunday June 6th @ 3pm UTC

https://timee.io/20210606T1500?tl=I%20LOVE%20ALGO%20Tournament&ln=https%3A%2F%2Fnanoroyale.com

Format:

Competitors will play in faucet games (expect 5-7 players per game) until enough of them have qualified to the next round. To qualify, players will need to accrue 10 points (win = 4 points,kills = 1 point). The process will repeat until there are 4 players left. These last 4 players will battle it out in 1v1s. Two semifinals (best of 7), followed by the grand final (best of 9).

How you can join:

Step 1: Join the Nano Royale discord server


r/algorand • • Sep 14 '21

Come over to algorand: a blockchain that can’t be shut down

Post image
542 Upvotes

r/algorand • • Sep 08 '21

I should be sleeping, but I can't stop watching this ridiculous climb.

Post image
538 Upvotes

r/algorand • • Oct 25 '21

Got it

Post image
535 Upvotes

r/algorand • • Oct 13 '21

Unpopular opinion: You don't need to show us your Governance screens.

518 Upvotes

Really though.. Your position is your business. This weird trend where everybody wants a pat on the back for every move they make is pretty cringe.


r/algorand • • Nov 21 '21

Meme Someday they'll come around...

Post image
509 Upvotes

r/algorand • • Jun 03 '21

Which one of you did this?

Post image
507 Upvotes

r/algorand • • Sep 06 '21

Well guys it’s been nice having you, but I’m gonna sell.

506 Upvotes

My wife just got out of the hospital and is on bed rest for 6 months, my hours have went to shit. I have to sell, and at least I’ll make a profit, but I hope you guys nothing but the best. I hope it soars to the moon and you guys are all filthy rich! Good luck to you guys!

Edit: I didn’t say this for anything, I was just trying to get it off my chest because I really do love algo, and this community. Yet some members sent me some algo, and it is the nicest thing anyone has done for me. Thank you guys, and I’ll hold this.

Edit 2: thank you guys who hooked me up with some algo so I could still have some sort of a bag. You guys are really nice and I will pay it forward when I’m back on my feet. Thanks to all of you.


r/algorand • • Aug 16 '21

Yup

Post image
504 Upvotes

r/algorand • • May 19 '21

Is that all you got?

Post image
501 Upvotes

r/algorand • • May 18 '22

General Last week Binance ran out of Algorand and had to pull the 2nd largest wallet enrolled in governance. As a result they will miss out on at least 1.8 million Algo's that now gets distributed to the rest of the governors.

Post image
500 Upvotes