Bitcoin Cash rewards (anti inflationist points) if people could get from merchants when they buy would accelerate adoption. Air miles, PC Points, SaveOnFoods points ect keep losing value here in Canada.
EDIT : Thanks to everybody for pointing out the few mistakes/improvements that can be made in this new-player level guide. For the sake of summarizing here : - Intel documents are NOT worth 250k. I didn't check them on the flea before writing this and for some reason I always remembered them at 250k. Game is in maintenance so I can't check the real price. That being said, it's still profitable to craft USB into Intel, it's just not x2 profitable. - Scav case : moonshine / intel docs, some people seem to say they've never been profitable. I personally *did not* measure those, I eyeballed it. I'm working on so much shit that I didn't bother. On average I think that I'm in a net positive, but it's as believable as people saying they're not : without proof we can't really say for sure. That bein said, it's certainly more profitable to run lower-tier scav runs that are *faster* when you're online, and to run a moonshine or intel when you log off. It's more efficient to get a lot of runs while you can re-start them every time. - Crafting moonshine : It's not profitable to spam it ; I was under the assumption that the average player who will read this will usually not play for 4-5 hours straight and will end up collecting yesterday's moonshine, craft a new one, and that's it. If that's you're rythm then yes, spam it. If you intend to play more than one craft worth's of time, then you will craft moonshine faster than you can spend it, and it's not really worth to sell it on the flea except to up your market reputation for a small loss (about 10k). So in short : craft moonshine to be able to start a moonshine run for when you log off, but you don't *need* more than that.
Check this out
Here is some actual data on the lavatory !! Hey everybody ! I know it can be a struggle to get a stable economy in this game, especially when you die a lot. Today I'm gonna try and give a few guidelines on how to make money safely, efficiently, fast, or in any other way we can think of. If you're struggling to stay above the 15-20 million rouble treshold, this guide is definitely for you. Very often I'll hear newer players say "Damn I can't seem to make money, I keep loosing. Every time I take gear I die instantly". There is some truth in that. Today I'll help you improve your survival rate, but most importantly I'll unbalance the other side of the equation. When you complain about losing a lot of money, I will help you spend less by a significant margin, as well as earn more. You'll also get rid of gear fera naturally. Remember this throughout this very, very long read : It all depends on how you want to play, and how much. Some of these tips will not fit how you want to play the game, and like Nikita always says : this game is supposed to be fun before anything else.
Safety Score : 100% Reward : Moderate but very stable. Maxing your hideout should be one of your top priorities, probably before telling your mom how much you love her every now and then. If you're not doing either of those, the big gamer in you knows what to do. Early wipe, save your fuel for when you're online and playing. If you're playing, your generator should definitely be running and all your stations should be crafting something. Once you have Medstation 1, Workbench 1 and Lavatory 2, you really have no reason to turn your generator off when you're playing. Once you have the bitcoin farm, you should never turn off the generator. Medstation : Craft salewas and/or IFAKs permanently. They cost 8k and sell for 15k. That's a net profit of about 25k / hour for salewas, as well as never having to buy any. Lavatory : Always be crafting Bleach. If you have 2 empty blue fuel, use those empty cans to craft a Magazine case. You can then keep the magazine cases until you've enough for your liking and sell those for a good profit. The bleach you will use to buy the 6B47 helmets which are better than the SSh-68 helmets. Buying from 2x bleach barter at ragman level 1 means you get the helmet for 18k (instead of 33k on the market). This helmet has better head coverage, less slow/negative effects, less weight, has a slot for a mount, has +11 ergonomics AND is cheaper than the 22k SSh-68. That being said, it has a slight noise reduction that the Ssh does not have. If you wear headphones I'd say this is negligible but debatable. I prefer to have the extra protection and ergonomics for sure, considering it's slightly cheaper. You can also barter for that helmet and instantly sell it back for a profit (five times) and level up ragman money requirements. Bleach can also be traded for the Blackjack backpack at level 4, as well as the TTV rig at level 2. You should definitely do it. Sell excess bleach on the flea market when the prices are around 10.5k or more. (around midnight Central European Time). Workbench : You can buy Power Cords and craft Wires forever and always make a profit. Buy in the morning and sell in the evening for better profits (CET timezone). For even more profit, you can craft gunpowders and ammo which tend to also be ridiculously pricy at night. Buying grenades from Peacekeeper and crafting green (Eagle) gunpowder is a good way to make a lot of money and level up Peacekeeper. Intel Center : You main objective is to get this one to level 3 for reduced fees and better quest rewards, but also access to the bitcoin farm at level 2. If you need FiR for quests, craft that. When you're done craft Intel Documents at all times (buy the USB), and use it for scav case or sell for a x2 profit. ( 3x40 for USB = 120, documents sell for 250) Bitcoin Farm : Once you have it, spend all your money on GPU until its maxxed, then level it up even more. The BTC farm is definitely worth it. At 50GPU you need to connect every 15 hours to clic. If you can't, keep it level 2 and connect every 24 hours to clic. Even at level 1 its worth. But its much, much faster at higher levels. From 0 to 50 GPUs it takes about 30 days to pay for itself. GPUs should not be sold until you maxxed it. Water Collector : Must be running at all times. Buy the components if you don't have them. Booze Generator : Must be running at all times. Buy the components if you don't have them. Scav Case : Always have it running on moonshine, and use intel documents once you're done crafting one. Nutrition Unit : It's not really worth crafting sugar to put in the Booze gen, as the price for chocolate is pretty much = the price of sugar. So buy the sugar instead and craft something else. I tend to craft Hot Rods when the prices are good (morning) and then use them to barter 5.45 BS Ammo with Prapor or sell for a profit. If you do all that, you should have about 150k an hour fairly easily. Don't forget to check it between every raid.
Safety Score : 100% Reward : Quite good. Once your mom has received all the love she deserves and your hideout is taken care of, you should have max traders (traders are a requirement for most of the hideout anyway). Traders level 4 will net you much better prices on most mods and open very good barter trades. Buy as much as you can from barter trades. You can buy almost everything from it, and it's usually at least 25% cheaper to buy the requirements and then do the barter. Ragman4 has the CPC Armored Rig which is level 5 armor, you'll get it for about 200k instead of 250k on the flea. The Slick is also much cheaper. The Blackjack backpack is literally half priced. You can also NOT use what you barter and just sell it back to a dealer (sometimes the same from which you bartered) for a profit as well as having 2 times the loyalty money increase (from bartering then from selling). Another good example is buying a Recbat 14k from the market, getting an ADAR for skier, selling it to Mechanic and winning 8k just like that. You can find every single barter that nets a profit yourself and just buy-resell and you'll probably make another 100k every reset, if you really are struggling and have the patience. I personally advise to just use the equipment for yourself unless you're levelling traders, but I wouldn't go as far as buying all profitable items every reset. Every trader at every level has good barters. You can make a full decent kit at level 1 traders for about 40k roubles on barter, instead of 90 if you buy it all. (Paca for masks, helmet for bleach, ADAR for recbatt, salewa from craft, backpack, etc. all barters) Bleach is beautiful and is coveted in the real world for its ability to cure diseases.
Safety Score : 100% Reward : Very profitable. Don't mod out of your reach. Don't mod Meta. If money is an issue for you, having +1 ergo won't change your life. For example, Priced at 10k roubles Priced at 45k Roubles See where I'm going with this? If you have money, sure, go for the Shift. If you wanna have fun and try, sure, go for it as well. But if you're struggling, buy 4 cobras and mod 4 guns for the price of 1% recoil which will not make you a gamer god anyway. Also, do NOT buy mods from the flea market when you see you can buy them from traders. Look at the top of the market, if the mod is greyed out, look at the price. It means you don't have access (yet). If the price is too inflated for you, find another mod. There are always other mods. You can make 2 AKMs that have a difference of 2% recoil and 4 Ergonomics and have a 150k price difference. It's up to you. When money is the issue, this was the answer. Note : Some guns are inherently much more expensive. Guns shooting 5.56 or 5.45 tend to be more expensive than 7.62. AKMs are VERY good budget guns. They're a bit harder to handle, but you can get a fully modded AK for 150-200k, where as you will have an entry level M4 for that price. 7.62 PS ammo is also incredibly cheap while being decent. Play 7.62 if you're struggling with money. It's not meta, but it's far more than enough, trust me. You'll rarely lose fights exclusively because you had PS ammo in an AKM. Rarely.
How much you usually extract with, on average, per map
How much you usually go in raid with, on average, per map
These will help us measure how much you fuck up or not. Lets make it simple. If you have a 500k loadout and you usually extract with 100k, at 10% survival rate, that means you will spend 500k x 10 = 5.000.000 roubles over 10 raids on average, die 9 times, and earn 100k once. This very obvious example shows the loss. Basically we're gonna try and balance that equation so that you never lose money on average. You'll have ups and downs obviously, but over a week or two, it'll smooth things out for you, like math always does in a pleasant conversation with a girl. So what can you do to improve that equation ?
4.1 Improve survival rate
Seems simple enough, DIE LESS. You do not need to be good, smart, or special to die less. If you die a lot, do something different. If you die less, try more of that. Explore statistical advantages through different gameplay. What can you do to die less practically? Here is a list of checkboxes you can tick depending on your money, skill, mood, or any other factor like the map and sheer luck:
Fight from a bigger distance. People miss more from far (so will you, but killing less is irrelevant when you want to die less)
Fight with better gear (supressed, better armor, better ammo, etc.). Its expensive, but it technically helps
Don't fight at all. Avoid fights, run away from gunshots. 99.3% of people who didn't get shot survive a raid.
Wait more, play slowly. If you go with the flow of players, you'll be with the players. Avoid that "wave" and stay behind it. When you come across players trying to extract to where you spawned, hide.
Play with friends if you have any. If not, your mom loves you and so do I. I do coaching so do a lot of other decent players, look it up.
Whenever you die, look at what killed you. Did you take a risk ? Did you lack skill ? Were you out of position ? Were you unlucky ? Try to be as OBJECTIVE as possible even in the frustration. It's pretty much always your fault if you died, avoid toxicity and learn something from that instead. If you took a fight with good gear and ammo and just lost, its probably skill/positioning. It's fine. Learn the game, fight differently, and with time it'll get better. If you were in the open, don't go in the open. If you were sprinting in the middle of interchange and got ambushed, well. Don't do that. Learn.
Do all that, it'll give you a LOT of data to actually improve by just doing something different without really being fastestronger, just smarter. And I repeat : you can do some of it, all of it, it depends on what you like, what you're comfortable with, and the time/investment you're putting in the game. It's okay to play at your own pace.
4.2 Reduce gear cost
The second part of our "profit equation" above is how much gear you take with you. Using previous tips, reduce that cost. Barters, cheaper mods, etc.
4.3 Increase extracted value
This one is not as tricky as it sounds. Basically there are two ways to extract with more money in the backpack :
Know what/where to loot
Have a bigger backpack.
The goal is to pay for the gear you will loose when you die while making a profit on top. That one time you extract if you have a MBSS backpack, you'll need items worth like 50k per slot to break even. If you take a tri-zip, suddenly it's only 30k per slot. If you take a blackjack and blackrock from good old ragman, suddenly it's 10k per slot. So you can break even by looting crickents and DVD players almost. See where I'm going ? Always take a tri-zip or bigger unless you're doing something special. That way you can afford to loot shitty areas, take less risk, and survive more while having a little less value. We'll cover that in a minute, but there are ways to loot high value items, moderate value and low value. Those have also different risk/reward. All of those are also map specific. In woods I'll often go with a 6B3TM armored rig for 40k, no helmet, 20k headphones and a sniper rifle. Rest is pouched so does not count. That's less than 100k investment. All players tend to have low value gear so I never extract with a lot either so it balances out. But on Woods, my survival rate is 20% instead of my overall 40%. So I know it's not a map I can reliably make money on, because I measured that accurately over time. This example is very common and should make sense to you. Same goes for interchange where I have more about 50% survival but will tend to go in with 600k worth of gear, but will also often extract with over 500k quite regularly. Different ratios, different values, different purposes. You can measure your own data if you're willing to do so, or you can eyeball it. Eyeballing it is much faster but very inaccurate because you will tend to include emotions in the mix when you die. You'll remember losses ~2x more than your wins (that's somewhat scientifically proven), and if you're eyeballing your loadout you might think you have 600k but really you might have only 450k. I would advise to go hardcore and measure it all for price, initial loadout, losses and earnings, for each map.
5. Money runs
Now money runs are vast and numerous. All include different levels of risk and reward. It's up to you once again to find what you're willing to do for the time it takes, the fun it will give you and how much it will actually help you. You can always try them all for ~50 raids the sake of trying something different and see how your data is impacted. it doesn't have to be 50 in a row if you don't want to. As long as you keep track of it it can be over a whole wipe. You'd have your data ready for the next wipe :) Faster is better though.
5.1 Hatchling runs
Safety Score : 100% Reward : Very Variable. Mentally exhausting. Those are incredibly money efficient. You're investing a gear of 0 value, so whatever you extract with is 100% win, so you cannot possibly lose money that way. Is it fun? Is it rewarding? I don't care, to each is own. Statistcally speaking, hatchling runs are an efficient way to make money. They do however require a little bit of knowledge, but not skill. You'll be much more efficient at doing these kind of runs if you know where to go, what to look for, and how to get there depending on your spawn. That being said, such knoweldge is easily found ; it's nothing complex, it just takes time to learn. Once again, depends on how much you're willing to invest (if not roubles, time).
5.2 Scav runs
Safety Score : 100% Reward : Low-ish Scav runs are also incredibly efficient for the same reason as hatchlings. Except those have a cooldown. Statisticall speaking I have noticed you should always run your scavs as fast as possible on the map where you extract both the fastest and most frequently. The explanation is simple, lets make it simpler : The scav is a button that makes you earn free money. When you press it the button becomes unpressable for some time, when you release the button you earn money (sometimes). That means you want to release the button as often as possible. And for that, you need to release it as fast as possible. It's that simple. So make scavs incredibly fast. I'm talking "Run through" fast. Unless you're looking for FiR items or doing something specific like annoying a streamer, you should literally run straight to the extract every single time, and loot what you have that doesn't make you go out of your way too much. Usually I suggest factory, go in, kill a random scav, loot it, get out. Two weapons is at LEAST 50k, 100 if they have a scope. There you go. That's 100k every 20 minutes (or less with intel center). That's MUCH BETTER than going up to 150-200k but taking 30 minutes to extract, and taking more risk by spending more time in the map. Every second you're in someone can shoot. Nobody can shoot you in the hideout. The exception to that rule is Scavs with a pilgrim which you can take on your favourite loot-run map, probably interchange or reserve. There you should just fill everything you can and extract once you're full, no matter what you have. 30 crickents and an extra gun is fine.
5.3 Stash runs
Safety Score : Very Reward : Okay Those are very very safe and can be done with a pistol and a backpack only. Very cheap, quite unchalleneged, for a moderate reward. Just go on a map that you like and run around and loot all stashes until you're full, then get out. You can vary the map/route depending on the traffic of players. Interchange and shoreline are good contenders for that. It'll net you easy money. Not great money, but definitely safe.
5.4 Loot Runs
Safety Score : Moderate Reward : Quite alright Once you have better knowledge/skill you can start having a specific route in a specific map, depending on a specific spawn. So it'll take time to learn. Usually very similar than a hatchling run except this time you bring moderate gear and go for moderate loots. For example, instead of going for fast techlight, in-and-out interchange, you can decide "alright I'll loot 100% of Oli and the computers in the back", it'll take time, but it'll make good loot. More money than stashes, definitely will see scavs to kill, and most probably some more pvp. More risk. If you win that PvP you have even more loot as well. But overall good reward. Loot runs need to be "scheduled" and thought of after several tries, so you know how much you can take per person depending on backpack size. For example you can't say "lets loot oli" if you have a 5-man with blackjacks, you'll all be empty. Adapt.
Safety Score : Insane Reward : Unreliably moderate This one is pretty obvious. Very risky, unpredictable rewards. Usually better than loot runs when you survive. I won't elaborate on this, because if you're reading this far you're probably struggling in PvP. And the rest of this guide already covers a fair bit.
Safety Score : "Meh" Reward : Very profitable. Now this is very, very important. Always insure your gear. Always. If you die you will get stuff back, pretty much for free. If you're really struggling people won't loot your "trash", so you WILL get it back. If you play in a group it's very likely that people will hide your stuff too. And most importantly : you can insurance fraud. This is the best way to balance the equation we talked about earlier. If you find a decent-ish gun, replace yours. You drop your initial investment by a significant margin, you will definitely get it back, and if you extract it's a flat profit. Weapons don't take inventory slot, so if you have two weapons that are not yours initially they will usually pay for your whole gear. I have quite often left my super-mega-modded HK just for an average M4 or other weapon that I can fight with, just so I can reduce my investment by 350k and up my reward by like 200k instantly. Replace your headphones all the time too, that's an easy -30+30k, same with helmets. even if it's a bit broken or slightly worse. If you're struggling with money, try to leave every raid with at least 3-4 pars of your equipment that aren't yours initially. But value the risk behind this. I won't leave my slick for a Paca at the third minute of a raid just to have that extra 28k. I won't leave my meta-modded HK for a naked mosin. But if it seems decent/doable, do it. It will pay off. Because even if you die, you still get your shit back, and gun is usually the most expensive part of the gear.
7. Final notes
It's all about balance. Find what works *for you* and try shit out. Really, try. You'll die, you'll learn, you'll adapt with data to back that up. I find it crazy that people will die and not try to learn from it. That's how you will improve as a player. First you gotta get smarter, then you'll get better. And with time, skill, mechanics, gamesense, all that will improve on the side. Earning more will snowball in your favour. And if you know you're statistically okay, you will have a much smaller gear fear and enjoy the game more. Sorry for the wall of text, you guys should be used to it with me by now :D I made these guides in video but not in english, so here I am typing it all for you guys. Enjoy :)
Ultimate glossary of crypto currency terms, acronyms and abbreviations
A common sentiment is brewing online; a shared desire for the internet that might have been. After decades of corporate encroachment, you don't need to be a power user to realize that something has gone very wrong. In the early days of the internet, the future was bright. In that future, when you sent an instant message, it traveled directly to the recipient. When you needed to pay a friend, you announced a transfer of value to their public key. When an app was missing a feature you wanted, you opened up the source code and implemented it. When you took a picture on your phone, it was immediately encrypted and backed up to storage that you controlled. In that future, people would laugh at the idea of having to authenticate themselves to some corporation before doing these things. What did we get instead? Rather than a network of human-sized communities, we have a handful of enormous commons, each controlled by a faceless corporate entity. Hey user, want to send a message? You can, but we'll store a copy of it indefinitely, unencrypted, for our preference-learning algorithms to pore over; how else could we slap targeted ads on every piece of content you see? Want to pay a friend? You can—in our Monopoly money. Want a new feature? Submit a request to our Support Center and we'll totally maybe think about it. Want to backup a photo? You can—inside our walled garden, which only we (and the NSA, of course) can access. Just be careful what you share, because merely locking you out of your account and deleting all your data is far from the worst thing we could do. You rationalize this: "MEGACORP would never do such a thing; it would be bad for business." But we all know, at some level, that this state of affairs, this inversion of power, is not merely "unfortunate" or "suboptimal" – No. It is degrading. Even if MEGACORP were purely benevolent, it is degrading that we must ask its permission to talk to our friends; that we must rely on it to safeguard our treasured memories; that our digital lives are completely beholden to those who seek only to extract value from us. At the root of this issue is the centralization of data. MEGACORP can surveil you—because your emails and video chats flow through their servers. And MEGACORP can control you—because they hold your data hostage. But centralization is a solution to a technical problem: How can we make the user's data accessible from anywhere in the world, on any device? For a long time, no alternative solution to this problem was forthcoming. Today, thanks to a confluence of established techniques and recent innovations, we have solved the accessibility problem without resorting to centralization. Hashing, encryption, and erasure encoding got us most of the way, but one barrier remained: incentives. How do you incentivize an anonymous stranger to store your data? Earlier protocols like BitTorrent worked around this limitation by relying on altruism, tit-for-tat requirements, or "points" – in other words, nothing you could pay your electric bill with. Finally, in 2009, a solution appeared: Bitcoin. Not long after, Sia was born. Cryptography has unleashed the latent power of the internet by enabling interactions between mutually-distrustful parties. Sia harnesses this power to turn the cloud storage market into a proper marketplace, where buyers and sellers can transact directly, with no intermediaries, anywhere in the world. No more silos or walled gardens: your data is encrypted, so it can't be spied on, and it's stored on many servers, so no single entity can hold it hostage. Thanks to projects like Sia, the internet is being re-decentralized. Sia began its life as a startup, which means it has always been subjected to two competing forces: the ideals of its founders, and the profit motive inherent to all businesses. Its founders have taken great pains to never compromise on the former, but this often threatened the company's financial viability. With the establishment of the Sia Foundation, this tension is resolved. The Foundation, freed of the obligation to generate profit, is a pure embodiment of the ideals from which Sia originally sprung. The goals and responsibilities of the Foundation are numerous: to maintain core Sia protocols and consensus code; to support developers building on top of Sia and its protocols; to promote Sia and facilitate partnerships in other spheres and communities; to ensure that users can easily acquire and safely store siacoins; to develop network scalability solutions; to implement hardforks and lead the community through them; and much more. In a broader sense, its mission is to commoditize data storage, making it cheap, ubiquitous, and accessible to all, without compromising privacy or performance. Sia is a perfect example of how we can achieve better living through cryptography. We now begin a new chapter in Sia's history. May our stewardship lead it into a bright future.
Today, we are proposing the creation of the Sia Foundation: a new non-profit entity that builds and supports distributed cloud storage infrastructure, with a specific focus on the Sia storage platform. What follows is an informal overview of the Sia Foundation, covering two major topics: how the Foundation will be funded, and what its funds will be used for.
The Sia Foundation will be structured as a non-profit entity incorporated in the United States, likely a 501(c)(3) organization or similar. The actions of the Foundation will be constrained by its charter, which formalizes the specific obligations and overall mission outlined in this document. The charter will be updated on an annual basis to reflect the current goals of the Sia community. The organization will be operated by a board of directors, initially comprising Luke Champine as President and Eddie Wang as Chairman. Luke Champine will be leaving his position at Nebulous to work at the Foundation full-time, and will seek to divest his shares of Nebulous stock along with other potential conflicts of interest. Neither Luke nor Eddie personally own any siafunds or significant quantities of siacoin.
The primary source of funding for the Foundation will come from a new block subsidy. Following a hardfork, 30 KS per block will be allocated to the "Foundation Fund," continuing in perpetuity. The existing 30 KS per block miner reward is not affected. Additionally, one year's worth of block subsidies (approximately 1.57 GS) will be allocated to the Fund immediately upon activation of the hardfork. As detailed below, the Foundation will provably burn any coins that it cannot meaningfully spend. As such, the 30 KS subsidy should be viewed as a maximum. This allows the Foundation to grow alongside Sia without requiring additional hardforks. The Foundation will not be funded to any degree by the possession or sale of siafunds. Siafunds were originally introduced as a means of incentivizing growth, and we still believe in their effectiveness: a siafund holder wants to increase the amount of storage on Sia as much as possible. While the Foundation obviously wants Sia to succeed, its driving force should be its charter. Deriving significant revenue from siafunds would jeopardize the Foundation's impartiality and focus. Ultimately, we want the Foundation to act in the best interests of Sia, not in growing its own budget.
The Foundation inherits a great number of responsibilities from Nebulous. Each quarter, the Foundation will publish the progress it has made over the past quarter, and list the responsibilities it intends to prioritize over the coming quarter. This will be accompanied by a financial report, detailing each area of expenditure over the past quarter, and forecasting expenditures for the coming quarter. Below, we summarize some of the myriad responsibilities towards which the Foundation is expected to allocate its resources.
Maintain and enhance core Sia software
Arguably, this is the most important responsibility of the Foundation. At the heart of Sia is its consensus algorithm: regardless of other differences, all Sia software must agree upon the content and rules of the blockchain. It is therefore crucial that the algorithm be stewarded by an entity that is accountable to the community, transparent in its decision-making, and has no profit motive or other conflicts of interest. Accordingly, Sia’s consensus functionality will no longer be directly maintained by Nebulous. Instead, the Foundation will release and maintain an implementation of a "minimal Sia full node," comprising the Sia consensus algorithm and P2P networking code. The source code will be available in a public repository, and signed binaries will be published for each release. Other parties may use this code to provide alternative full node software. For example, Nebulous may extend the minimal full node with wallet, renter, and host functionality. The source code of any such implementation may be submitted to the Foundation for review. If the code passes review, the Foundation will provide "endorsement signatures" for the commit hash used and for binaries compiled internally by the Foundation. Specifically, these signatures assert that the Foundation believes the software contains no consensus-breaking changes or other modifications to imported Foundation code. Endorsement signatures and Foundation-compiled binaries may be displayed and distributed by the receiving party, along with an appropriate disclaimer. A minimal full node is not terribly useful on its own; the wallet, renter, host, and other extensions are what make Sia a proper developer platform. Currently, the only implementations of these extensions are maintained by Nebulous. The Foundation will contract Nebulous to ensure that these extensions continue to receive updates and enhancements. Later on, the Foundation intends to develop its own implementations of these extensions and others. As with the minimal node software, these extensions will be open source and available in public repositories for use by any Sia node software. With the consensus code now managed by the Foundation, the task of implementing and orchestrating hardforks becomes its responsibility as well. When the Foundation determines that a hardfork is necessary (whether through internal discussion or via community petition), a formal proposal will be drafted and submitted for public review, during which arguments for and against the proposal may be submitted to a public repository. During this time, the hardfork code will be implemented, either by Foundation employees or by external contributors working closely with the Foundation. Once the implementation is finished, final arguments will be heard. The Foundation board will then vote whether to accept or reject the proposal, and announce their decision along with appropriate justification. Assuming the proposal was accepted, the Foundation will announce the block height at which the hardfork will activate, and will subsequently release source code and signed binaries that incorporate the hardfork code. Regardless of the Foundation's decision, it is the community that ultimately determines whether a fork is accepted or rejected – nothing can change that. Foundation node software will never automatically update, so all forks must be explicitly adopted by users. Furthermore, the Foundation will provide replay and wipeout protection for its hard forks, protecting other chains from unintended or malicious reorgs. Similarly, the Foundation will ensure that any file contracts formed prior to a fork activation will continue to be honored on both chains until they expire. Finally, the Foundation also intends to pursue scalability solutions for the Sia blockchain. In particular, work has already begun on an implementation of Utreexo, which will greatly reduce the space requirements of fully-validating nodes (allowing a full node to be run on a smartphone) while increasing throughput and decreasing initial sync time. A hardfork implementing Utreexo will be submitted to the community as per the process detailed above. As this is the most important responsibility of the Foundation, it will receive a significant portion of the Foundation’s budget, primarily in the form of developer salaries and contracting agreements.
Support community services
We intend to allocate 25% of the Foundation Fund towards the community. This allocation will be held and disbursed in the form of siacoins, and will pay for grants, bounties, hackathons, and other community-driven endeavours. Any community-run service, such as a Skynet portal, explorer or web wallet, may apply to have its costs covered by the Foundation. Upon approval, the Foundation will reimburse expenses incurred by the service, subject to the exact terms agreed to. The intent of these grants is not to provide a source of income, but rather to make such services "break even" for their operators, so that members of the community can enrich the Sia ecosystem without worrying about the impact on their own finances.
Ensure easy acquisition and storage of siacoins
Most users will acquire their siacoins via an exchange. The Foundation will provide support to Sia-compatible exchanges, and pursue relevant integrations at its discretion, such as Coinbase's new Rosetta standard. The Foundation may also release DEX software that enables trading cryptocurrencies without the need for a third party. (The Foundation itself will never operate as a money transmitter.) Increasingly, users are storing their cryptocurrency on hardware wallets. The Foundation will maintain the existing Ledger Nano S integration, and pursue further integrations at its discretion. Of course, all hardware wallets must be paired with software running on a computer or smartphone, so the Foundation will also develop and/or maintain client-side wallet software, including both full-node wallets and "lite" wallets. Community-operated wallet services, i.e. web wallets, may be funded via grants. Like core software maintenance, this responsibility will be funded in the form of developer salaries and contracting agreements.
Protect the ecosystem
When it comes to cryptocurrency security, patching software vulnerabilities is table stakes; there are significant legal and social threats that we must be mindful of as well. As such, the Foundation will earmark a portion of its fund to defend the community from legal action. The Foundation will also safeguard the network from 51% attacks and other threats to network security by implementing softforks and/or hardforks where necessary. The Foundation also intends to assist in the development of a new FOSS software license, and to solicit legal memos on various Sia-related matters, such as hosting in the United States and the EU. In a broader sense, the establishment of the Foundation makes the ecosystem more robust by transferring core development to a more neutral entity. Thanks to its funding structure, the Foundation will be immune to various forms of pressure that for-profit companies are susceptible to.
Drive adoption of Sia
Although the overriding goal of the Foundation is to make Sia the best platform it can be, all that work will be in vain if no one uses the platform. There are a number of ways the Foundation can promote Sia and get it into the hands of potential users and developers. In-person conferences are understandably far less popular now, but the Foundation can sponsor and/or participate in virtual conferences. (In-person conferences may be held in the future, permitting circumstances.) Similarly, the Foundation will provide prizes for hackathons, which may be organized by community members, Nebulous, or the Foundation itself. Lastly, partnerships with other companies in the cryptocurrency space—or the cloud storage space—are a great way to increase awareness of Sia. To handle these responsibilities, one of the early priorities of the Foundation will be to hire a marketing director.
The Foundation Fund will be controlled by a multisig address. Each member of the Foundation's board will control one of the signing keys, with the signature threshold to be determined once the final composition of the board is known. (This threshold may also be increased or decreased if the number of board members changes.) Additionally, one timelocked signing key will be controlled by David Vorick. This key will act as a “dead man’s switch,” to be used in the event of an emergency that prevents Foundation board members from reaching the signature threshold. The timelock ensures that this key cannot be used unless the Foundation fails to sign a transaction for several months. On the 1st of each month, the Foundation will use its keys to transfer all siacoins in the Fund to two new addresses. The first address will be controlled by a high-security hot wallet, and will receive approximately one month's worth of Foundation expenditures. The second address, receiving the remaining siacoins, will be a modified version of the source address: specifically, it will increase the timelock on David Vorick's signing key by one month. Any other changes to the set of signing keys, such as the arrival or departure of board members, will be incorporated into this address as well. The Foundation Fund is allocated in SC, but many of the Foundation's expenditures must be paid in USD or other fiat currency. Accordingly, the Foundation will convert, at its discretion, a portion of its monthly withdrawals to fiat currency. We expect this conversion to be primarily facilitated by private "OTC" sales to accredited investors. The Foundation currently has no plans to speculate in cryptocurrency or other assets. Finally, it is important that the Foundation adds value to the Sia platform well in excess of the inflation introduced by the block subsidy. For this reason, the Foundation intends to provably burn, on a quarterly basis, any coins that it cannot allocate towards any justifiable expense. In other words, coins will be burned whenever doing so provides greater value to the platform than any other use. Furthermore, the Foundation will cap its SC treasury at 5% of the total supply, and will cap its USD treasury at 4 years’ worth of predicted expenses. Addendum: Hardfork Timeline We would like to see this proposal finalized and accepted by the community no later than September 30th. A new version of siad, implementing the hardfork, will be released no later than October 15th. The hardfork will activate at block 293220, which is expected to occur around 12pm EST on January 1st, 2021.
Addendum: Inflation specifics The total supply of siacoins as of January 1st, 2021 will be approximately 45.243 GS. The initial subsidy of 1.57 GS thus increases the supply by 3.47%, and the total annual inflation in 2021 will be at most 10.4% (if zero coins are burned). In 2022, total annual inflation will be at most 6.28%, and will steadily decrease in subsequent years.
We see the establishment of the Foundation as an important step in the maturation of the Sia project. It provides the ecosystem with a sustainable source of funding that can be exclusively directed towards achieving Sia's ambitious goals. Compared to other projects with far deeper pockets, Sia has always punched above its weight; once we're on equal footing, there's no telling what we'll be able to achieve. Nevertheless, we do not propose this change lightly, and have taken pains to ensure that the Foundation will act in accordance with the ideals that this community shares. It will operate transparently, keep inflation to a minimum, and respect the user's fundamental role in decentralized systems. We hope that everyone in the community will consider this proposal carefully, and look forward to a productive discussion.
Cosmos is a heterogeneous network of many independent parallel blockchains, each powered by classical BFT consensus algorithms like Tendermint. Developers can easily build custom application specific blockchains, called Zones, through the Cosmos SDK framework. These Zones connect to Hubs, which are specifically designed to connect zones together. The vision of Cosmos is to have thousands of Zones and Hubs that are Interoperable through the Inter-Blockchain Communication Protocol (IBC). Cosmos can also connect to other systems through peg zones, which are specifically designed zones that each are custom made to interact with another ecosystem such as Ethereum and Bitcoin. Cosmos does not use Sharding with each Zone and Hub being sovereign with their own validator set. For a more in-depth look at Cosmos and provide more reference to points made in this article, please see my three part series — Part One, Part Two, Part Three (There's a youtube video with a quick video overview of Cosmos on the medium article - https://medium.com/ava-hub/comparison-between-avalanche-cosmos-and-polkadot-a2a98f46c03b)
Polkadot is a heterogeneous blockchain protocol that connects multiple specialised blockchains into one unified network. It achieves scalability through a sharding infrastructure with multiple blockchains running in parallel, called parachains, that connect to a central chain called the Relay Chain. Developers can easily build custom application specific parachains through the Substrate development framework. The relay chain validates the state transition of connected parachains, providing shared state across the entire ecosystem. If the Relay Chain must revert for any reason, then all of the parachains would also revert. This is to ensure that the validity of the entire system can persist, and no individual part is corruptible. The shared state makes it so that the trust assumptions when using parachains are only those of the Relay Chain validator set, and no other. Interoperability is enabled between parachains through Cross-Chain Message Passing (XCMP) protocol and is also possible to connect to other systems through bridges, which are specifically designed parachains or parathreads that each are custom made to interact with another ecosystem such as Ethereum and Bitcoin. The hope is to have 100 parachains connect to the relay chain. For a more in-depth look at Polkadot and provide more reference to points made in this article, please see my three part series — Part One, Part Two, Part Three (There's a youtube video with a quick video overview of Polkadot on the medium article - https://medium.com/ava-hub/comparison-between-avalanche-cosmos-and-polkadot-a2a98f46c03b)
Avalanche is a platform of platforms, ultimately consisting of thousands of subnets to form a heterogeneous interoperable network of many blockchains, that takes advantage of the revolutionary Avalanche Consensus protocols to provide a secure, globally distributed, interoperable and trustless framework offering unprecedented decentralisation whilst being able to comply with regulatory requirements. Avalanche allows anyone to create their own tailor-made application specific blockchains, supporting multiple custom virtual machines such as EVM and WASM and written in popular languages like Go (with others coming in the future) rather than lightly used, poorly-understood languages like Solidity. This virtual machine can then be deployed on a custom blockchain network, called a subnet, which consist of a dynamic set of validators working together to achieve consensus on the state of a set of many blockchains where complex rulesets can be configured to meet regulatory compliance. Avalanche was built with serving financial markets in mind. It has native support for easily creating and trading digital smart assets with complex custom rule sets that define how the asset is handled and traded to ensure regulatory compliance can be met. Interoperability is enabled between blockchains within a subnet as well as between subnets. Like Cosmos and Polkadot, Avalanche is also able to connect to other systems through bridges, through custom virtual machines made to interact with another ecosystem such as Ethereum and Bitcoin. For a more in-depth look at Avalanche and provide more reference to points made in this article, please see here and here (There's a youtube video with a quick video overview of Avalanche on the medium article - https://medium.com/ava-hub/comparison-between-avalanche-cosmos-and-polkadot-a2a98f46c03b)
Comparison between Cosmos, Polkadot and Avalanche
A frequent question I see being asked is how Cosmos, Polkadot and Avalanche compare? Whilst there are similarities there are also a lot of differences. This article is not intended to be an extensive in-depth list, but rather an overview based on some of the criteria that I feel are most important. For a more in-depth view I recommend reading the articles for each of the projects linked above and coming to your own conclusions. I want to stress that it’s not a case of one platform being the killer of all other platforms, far from it. There won’t be one platform to rule them all, and too often the tribalism has plagued this space. Blockchains are going to completely revolutionise most industries and have a profound effect on the world we know today. It’s still very early in this space with most adoption limited to speculation and trading mainly due to the limitations of Blockchain and current iteration of Ethereum, which all three of these platforms hope to address. For those who just want a quick summary see the image at the bottom of the article. With that said let’s have a look
Each Zone and Hub in Cosmos is capable of up to around 1000 transactions per second with bandwidth being the bottleneck in consensus. Cosmos aims to have thousands of Zones and Hubs all connected through IBC. There is no limit on the number of Zones / Hubs that can be created
Parachains in Polkadot are also capable of up to around 1500 transactions per second. A portion of the parachain slots on the Relay Chain will be designated as part of the parathread pool, the performance of a parachain is split between many parathreads offering lower performance and compete amongst themselves in a per-block auction to have their transactions included in the next relay chain block. The number of parachains is limited by the number of validators on the relay chain, they hope to be able to achieve 100 parachains.
Avalanche is capable of around 4500 transactions per second per subnet, this is based on modest hardware requirements to ensure maximum decentralisation of just 2 CPU cores and 4 GB of Memory and with a validator size of over 2,000 nodes. Performance is CPU-bound and if higher performance is required then more specialised subnets can be created with higher minimum requirements to be able to achieve 10,000 tps+ in a subnet. Avalanche aims to have thousands of subnets (each with multiple virtual machines / blockchains) all interoperable with each other. There is no limit on the number of Subnets that can be created.
All three platforms offer vastly superior performance to the likes of Bitcoin and Ethereum 1.0. Avalanche with its higher transactions per second, no limit on the number of subnets / blockchains that can be created and the consensus can scale to potentially millions of validators all participating in consensus scores ✅✅✅. Polkadot claims to offer more tps than cosmos, but is limited to the number of parachains (around 100) whereas with Cosmos there is no limit on the number of hubs / zones that can be created. Cosmos is limited to a fairly small validator size of around 200 before performance degrades whereas Polkadot hopes to be able to reach 1000 validators in the relay chain (albeit only a small number of validators are assigned to each parachain). Thus Cosmos and Polkadot scores ✅✅ https://preview.redd.it/2o0brllyvpq51.png?width=1000&format=png&auto=webp&s=8f62bb696ecaafcf6184da005d5fe0129d504518
Tendermint consensus is limited to around 200 validators before performance starts to degrade. Whilst there is the Cosmos Hub it is one of many hubs in the network and there is no central hub or limit on the number of zones / hubs that can be created.
Polkadot has 1000 validators in the relay chain and these are split up into a small number that validate each parachain (minimum of 14). The relay chain is a central point of failure as all parachains connect to it and the number of parachains is limited depending on the number of validators (they hope to achieve 100 parachains). Due to the limited number of parachain slots available, significant sums of DOT will need to be purchased to win an auction to lease the slot for up to 24 months at a time. Thus likely to lead to only those with enough funds to secure a parachain slot. Parathreads are however an alternative for those that require less and more varied performance for those that can’t secure a parachain slot.
Avalanche consensus scan scale to tens of thousands of validators, even potentially millions of validators all participating in consensus through repeated sub-sampling. The more validators, the faster the network becomes as the load is split between them. There are modest hardware requirements so anyone can run a node and there is no limit on the number of subnets / virtual machines that can be created.
Avalanche offers unparalleled decentralisation using its revolutionary consensus protocols that can scale to millions of validators all participating in consensus at the same time. There is no limit to the number of subnets and virtual machines that can be created, and they can be created by anyone for a small fee, it scores ✅✅✅. Cosmos is limited to 200 validators but no limit on the number of zones / hubs that can be created, which anyone can create and scores ✅✅. Polkadot hopes to accommodate 1000 validators in the relay chain (albeit these are split amongst each of the parachains). The number of parachains is limited and maybe cost prohibitive for many and the relay chain is a ultimately a single point of failure. Whilst definitely not saying it’s centralised and it is more decentralised than many others, just in comparison between the three, it scores ✅ https://preview.redd.it/ckfamee0wpq51.png?width=1000&format=png&auto=webp&s=c4355f145d821fabf7785e238dbc96a5f5ce2846
Tendermint consensus used in Cosmos reaches finality within 6 seconds. Cosmos consists of many Zones and Hubs that connect to each other. Communication between 2 zones could pass through many hubs along the way, thus also can contribute to latency times depending on the path taken as explained in part two of the articles on Cosmos. It doesn’t need to wait for an extended period of time with risk of rollbacks.
Polkadot provides a Hybrid consensus protocol consisting of Block producing protocol, BABE, and then a finality gadget called GRANDPA that works to agree on a chain, out of many possible forks, by following some simpler fork choice rule. Rather than voting on every block, instead it reaches agreements on chains. As soon as more than 2/3 of validators attest to a chain containing a certain block, all blocks leading up to that one are finalized at once. If an invalid block is detected after it has been finalised then the relay chain would need to be reverted along with every parachain. This is particularly important when connecting to external blockchains as those don’t share the state of the relay chain and thus can’t be rolled back. The longer the time period, the more secure the network is, as there is more time for additional checks to be performed and reported but at the expense of finality. Finality is reached within 60 seconds between parachains but for external ecosystems like Ethereum their state obviously can’t be rolled back like a parachain and so finality will need to be much longer (60 minutes was suggested in the whitepaper) and discussed in more detail in part three
Avalanche consensus achieves finality within 3 seconds, with most happening sub 1 second, immutable and completely irreversible. Any subnet can connect directly to another without having to go through multiple hops and any VM can talk to another VM within the same subnet as well as external subnets. It doesn’t need to wait for an extended period of time with risk of rollbacks.
With regards to performance far too much emphasis is just put on tps as a metric, the other equally important metric, if not more important with regards to finance is latency. Throughput measures the amount of data at any given time that it can handle whereas latency is the amount of time it takes to perform an action. It’s pointless saying you can process more transactions per second than VISA when it takes 60 seconds for a transaction to complete. Low latency also greatly increases general usability and customer satisfaction, nowadays everyone expects card payments, online payments to happen instantly. Avalanche achieves the best results scoring ✅✅✅, Cosmos with comes in second with 6 second finality ✅✅ and Polkadot with 60 second finality (which may be 60 minutes for external blockchains) scores ✅ https://preview.redd.it/kzup5x42wpq51.png?width=1000&format=png&auto=webp&s=320eb4c25dc4fc0f443a7a2f7ff09567871648cd
Every Zone and Hub in Cosmos has their own validator set and different trust assumptions. Cosmos are researching a shared security model where a Hub can validate the state of connected zones for a fee but not released yet. Once available this will make shared security optional rather than mandatory.
Shared Security is mandatory with Polkadot which uses a Shared State infrastructure between the Relay Chain and all of the connected parachains. If the Relay Chain must revert for any reason, then all of the parachains would also revert. Every parachain makes the same trust assumptions, and as such the relay chain validates state transition and enables seamless interoperability between them. In return for this benefit, they have to purchase DOT and win an auction for one of the available parachain slots. However, parachains can’t just rely on the relay chain for their security, they will also need to implement censorship resistance measures and utilise proof of work / proof of stake for each parachain as well as discussed in part three, thus parachains can’t just rely on the security of the relay chain, they need to ensure sybil resistance mechanisms using POW and POS are implemented on the parachain as well.
A subnet in Avalanche consists of a dynamic set of validators working together to achieve consensus on the state of a set of many blockchains where complex rulesets can be configured to meet regulatory compliance. So unlike in Cosmos where each zone / hub has their own validators, A subnet can validate a single or many virtual machines / blockchains with a single validator set. Shared security is optional
Shared security is mandatory in polkadot and a key design decision in its infrastructure. The relay chain validates the state transition of all connected parachains and thus scores ✅✅✅. Subnets in Avalanche can validate state of either a single or many virtual machines. Each subnet can have their own token and shares a validator set, where complex rulesets can be configured to meet regulatory compliance. It scores ✅ ✅. Every Zone and Hub in cosmos has their own validator set / token but research is underway to have the hub validate the state transition of connected zones, but as this is still early in the research phase scores ✅ for now. https://preview.redd.it/pbgyk3o3wpq51.png?width=1000&format=png&auto=webp&s=61c18e12932a250f5633c40633810d0f64520575
The Cosmos project started in 2016 with an ICO held in April 2017. There are currently around 50 projects building on the Cosmos SDK with a full list can be seen here and filtering for Cosmos SDK . Not all of the projects will necessarily connect using native cosmos sdk and IBC and some have forked parts of the Cosmos SDK and utilise the tendermint consensus such as Binance Chain but have said they will connect in the future.
The Polkadot project started in 2016 with an ICO held in October 2017. There are currently around 70 projects building on Substrate and a full list can be seen here and filtering for Substrate Based. Like with Cosmos not all projects built using substrate will necessarily connect to Polkadot and parachains or parathreads aren’t currently implemented in either the Live or Test network (Kusama) as of the time of this writing.
Avalanche in comparison started much later with Ava Labs being founded in 2018. Avalanche held it’s ICO in July 2020. Due to lot shorter time it has been in development, the number of projects confirmed are smaller with around 14 projects currently building on Avalanche. Due to the customisability of the platform though, many virtual machines can be used within a subnet making the process incredibly easy to port projects over. As an example, it will launch with the Ethereum Virtual Machine which enables byte for byte compatibility and all the tooling like Metamask, Truffle etc. will work, so projects can easily move over to benefit from the performance, decentralisation and low gas fees offered. In the future Cosmos and Substrate virtual machines could be implemented on Avalanche.
Whilst it’s still early for all 3 projects (and the entire blockchain space as a whole), there is currently more projects confirmed to be building on Cosmos and Polkadot, mostly due to their longer time in development. Whilst Cosmos has fewer projects, zones are implemented compared to Polkadot which doesn’t currently have parachains. IBC to connect zones and hubs together is due to launch Q2 2021, thus both score ✅✅✅. Avalanche has been in development for a lot shorter time period, but is launching with an impressive feature set right from the start with ability to create subnets, VMs, assets, NFTs, permissioned and permissionless blockchains, cross chain atomic swaps within a subnet, smart contracts, bridge to Ethereum etc. Applications can easily port over from other platforms and use all the existing tooling such as Metamask / Truffle etc but benefit from the performance, decentralisation and low gas fees offered. Currently though just based on the number of projects in comparison it scores ✅. https://preview.redd.it/4zpi6s85wpq51.png?width=1000&format=png&auto=webp&s=e91ade1a86a5d50f4976f3b23a46e9287b08e373
Cosmos enables permissioned and permissionless zones which can connect to each other with the ability to have full control over who validates the blockchain. For permissionless zones each zone / hub can have their own token and they are in control who validates.
With polkadot the state transition is performed by a small randomly selected assigned group of validators from the relay chain plus with the possibility that state is rolled back if an invalid transaction of any of the other parachains is found. This may pose a problem for enterprises that need complete control over who performs validation for regulatory reasons. In addition due to the limited number of parachain slots available Enterprises would have to acquire and lock up large amounts of a highly volatile asset (DOT) and have the possibility that they are outbid in future auctions and find they no longer can have their parachain validated and parathreads don’t provide the guaranteed performance requirements for the application to function.
Avalanche enables permissioned and permissionless subnets and complex rulesets can be configured to meet regulatory compliance. For example a subnet can be created where its mandatory that all validators are from a certain legal jurisdiction, or they hold a specific license and regulated by the SEC etc. Subnets are also able to scale to tens of thousands of validators, and even potentially millions of nodes, all participating in consensus so every enterprise can run their own node rather than only a small amount. Enterprises don’t have to hold large amounts of a highly volatile asset, but instead pay a fee in AVAX for the creation of the subnets and blockchains which is burnt.
Avalanche provides the customisability to run private permissioned blockchains as well as permissionless where the enterprise is in control over who validates the blockchain, with the ability to use complex rulesets to meet regulatory compliance, thus scores ✅✅✅. Cosmos is also able to run permissioned and permissionless zones / hubs so enterprises have full control over who validates a blockchain and scores ✅✅. Polkadot requires locking up large amounts of a highly volatile asset with the possibility of being outbid by competitors and being unable to run the application if the guaranteed performance is required and having to migrate away. The relay chain validates the state transition and can roll back the parachain should an invalid block be detected on another parachain, thus scores ✅. https://preview.redd.it/li5jy6u6wpq51.png?width=1000&format=png&auto=webp&s=e2a95f1f88e5efbcf9e23c789ae0f002c8eb73fc
Cosmos will connect Hubs and Zones together through its IBC protocol (due to release in Q1 2020). Connecting to blockchains outside of the Cosmos ecosystem would either require the connected blockchain to fork their code to implement IBC or more likely a custom “Peg Zone” will be created specific to work with a particular blockchain it’s trying to bridge to such as Ethereum etc. Each Zone and Hub has different trust levels and connectivity between 2 zones can have different trust depending on which path it takes (this is discussed more in this article). Finality time is low at 6 seconds, but depending on the number of hops, this can increase significantly.
Polkadot’s shared state means each parachain that connects shares the same trust assumptions, of the relay chain validators and that if one blockchain needs to be reverted, all of them will need to be reverted. Interoperability is enabled between parachains through Cross-Chain Message Passing (XCMP) protocol and is also possible to connect to other systems through bridges, which are specifically designed parachains or parathreads that each are custom made to interact with another ecosystem such as Ethereum and Bitcoin. Finality time between parachains is around 60 seconds, but longer will be needed (initial figures of 60 minutes in the whitepaper) for connecting to external blockchains. Thus limiting the appeal of connecting two external ecosystems together through Polkadot. Polkadot is also limited in the number of Parachain slots available, thus limiting the amount of blockchains that can be bridged. Parathreads could be used for lower performance bridges, but the speed of future blockchains is only going to increase.
A subnet can validate multiple virtual machines / blockchains and all blockchains within a subnet share the same trust assumptions / validator set, enabling cross chain interoperability. Interoperability is also possible between any other subnet, with the hope Avalanche will consist of thousands of subnets. Each subnet may have a different trust level, but as the primary network consists of all validators then this can be used as a source of trust if required. As Avalanche supports many virtual machines, bridges to other ecosystems are created by running the connected virtual machine. There will be an Ethereum bridge using the EVM shortly after mainnet. Finality time is much faster at sub 3 seconds (with most happening under 1 second) with no chance of rolling back so more appealing when connecting to external blockchains.
All 3 systems are able to perform interoperability within their ecosystem and transfer assets as well as data, as well as use bridges to connect to external blockchains. Cosmos has different trust levels between its zones and hubs and can create issues depending on which path it takes and additional latency added. Polkadot provides the same trust assumptions for all connected parachains but has long finality and limited number of parachain slots available. Avalanche provides the same trust assumptions for all blockchains within a subnet, and different trust levels between subnets. However due to the primary network consisting of all validators it can be used for trust. Avalanche also has a much faster finality time with no limitation on the number of blockchains / subnets / bridges that can be created. Overall all three blockchains excel with interoperability within their ecosystem and each score ✅✅. https://preview.redd.it/ai0bkbq8wpq51.png?width=1000&format=png&auto=webp&s=3e85ee6a3c4670f388ccea00b0c906c3fb51e415
The ATOM token is the native token for the Cosmos Hub. It is commonly mistaken by people that think it’s the token used throughout the cosmos ecosystem, whereas it’s just used for one of many hubs in Cosmos, each with their own token. Currently ATOM has little utility as IBC isn’t released and has no connections to other zones / hubs. Once IBC is released zones may prefer to connect to a different hub instead and so ATOM is not used. ATOM isn’t a fixed capped supply token and supply will continuously increase with a yearly inflation of around 10% depending on the % staked. The current market cap for ATOM as of the time of this writing is $1 Billion with 203 million circulating supply. Rewards can be earnt through staking to offset the dilution caused by inflation. Delegators can also get slashed and lose a portion of their ATOM should the validator misbehave.
Polkadot’s native token is DOT and it’s used to secure the Relay Chain. Each parachain needs to acquire sufficient DOT to win an auction on an available parachain lease period of up to 24 months at a time. Parathreads have a fixed fee for registration that would realistically be much lower than the cost of acquiring a parachain slot and compete with other parathreads in a per-block auction to have their transactions included in the next relay chain block. DOT isn’t a fixed capped supply token and supply will continuously increase with a yearly inflation of around 10% depending on the % staked. The current market cap for DOT as of the time of this writing is $4.4 Billion with 852 million circulating supply. Delegators can also get slashed and lose their DOT (potentially 100% of their DOT for serious attacks) should the validator misbehave.
AVAX is the native token for the primary network in Avalanche. Every validator of any subnet also has to validate the primary network and stake a minimum of 2000 AVAX. There is no limit to the number of validators like other consensus methods then this can cater for tens of thousands even potentially millions of validators. As every validator validates the primary network, this can be a source of trust for interoperability between subnets as well as connecting to other ecosystems, thus increasing amount of transaction fees of AVAX. There is no slashing in Avalanche, so there is no risk to lose your AVAX when selecting a validator, instead rewards earnt for staking can be slashed should the validator misbehave. Because Avalanche doesn’t have direct slashing, it is technically possible for someone to both stake AND deliver tokens for something like a flash loan, under the invariant that all tokens that are staked are returned, thus being able to make profit with staked tokens outside of staking itself. There will also be a separate subnet for Athereum which is a ‘spoon,’ or friendly fork, of Ethereum, which benefits from the Avalanche consensus protocol and applications in the Ethereum ecosystem. It’s native token ATH will be airdropped to ETH holders as well as potentially AVAX holders as well. This can be done for other blockchains as well. Transaction fees on the primary network for all 3 of the blockchains as well as subscription fees for creating a subnet and blockchain are paid in AVAX and are burnt, creating deflationary pressure. AVAX is a fixed capped supply of 720 million tokens, creating scarcity rather than an unlimited supply which continuously increase of tokens at a compounded rate each year like others. Initially there will be 360 tokens minted at Mainnet with vesting periods between 1 and 10 years, with tokens gradually unlocking each quarter. The Circulating supply is 24.5 million AVAX with tokens gradually released each quater. The current market cap of AVAX is around $100 million.
Should I take more risks with my money (eg investing)?
Hi I am living with my parents at 26. I may buy my first house in a year's time (or maybe just over a year). I'm in a fortunate position where I've saved up well over a number of years. I have approx £65k in savings on a £27k salary. My money is distributed into various accounts (originally for interest purposes although they've pretty much all dropped). The £65k also includes my money in my Lifetime ISA and just over £300 in Bitcoin which has been going up nicely in value. I'm generally a cautious person and tend to avoid risk, however sometimes in order to become wealthier you need to take risks. I'm in a very fortunate position where I have good savings and very low monthly outgoings (about £400 spend across the whole month). So effectively my 'emergency fund' is huge and would last me a long time. Obviously that'll change when I eventually buy my first house. Since I've reached a point where I shouldn't worry about moving into the next LTV bracket, I feel I don't need to focus as much on increasing my savings for a deposit (in liquid form). Despite me being a very cautious person, I was thinking to myself that if I invested say £4k and the investment didn't come off and I lost the majority of that money, it wouldn't put me in big financial trouble. However if the investment paid off and became £15k then I would be delighted. Ie the rewards could be greater than the money lost. Using my example, of course if I lost £4k I'd be upset but anyone would be! However, being upset is different to being in a disastrous financial situation (and fortunately losing the £4k wouldn't put me in that disastrous situation). I've also partly been put off investing (apart from the small amount I have in BTC) as I am looking to buy a place in 12-16 months. However, perhaps there are some shorter term investments I could even consider (I know generally stocks and share are long term investment eg 10 years so maybe I won't invest in these). An obvious one could be to put more money into the BTC which I believe will peak in value in September 2021. What do you think? Any insight would be much appreciated.
Do Autonomous Trucks dream of C.W. McCall? Part 9- a new home
Tran was a shitty gambler, Chi mused. He played poker like he was sure the next hand would save him. It didn’t. He overpromised and underpaid. Chi planned on kicking his ass to send a message, but Tran ran that line of shit about millions in bitcoin. Against his better judgment, Chi settled Tran’s debts with every other loan-shark in town and fronted another stack of cash. And all that ended with Tran gambling that away, talking a load of shit and ending up in this dumpster with a trash-bag tied around his neck. Chi looked at Tran’s phone and wondered if the money was ever real. Considering it might point back at him, he smashed it against the corner of the dumpster a few times before dropping it and walking back to his car. He had some debts to pay. Falstaff looked at the paper maps in the motel’s office. He followed the Interstate southeast to the desert and what used to be the California- Arizona border. He looked for places he hadn’t heard of being associated with edgy festivals. Even better, motels with chain-sounding names. That’s the place nobody’d look for him. He packed his car, coaxed Hank back in the carrier and got in his car. Before he got going, he booted his laptop and put the memory card back in. Evidence wasn’t a problem any more, it was getting found. He copied the contents to his laptop and poked around. Ten minutes later, he had set up a password cracker against the accounts, hoping that Tran would choose something easier to remember and therefore guessable. He plugged the laptop’s power supply into the car’s cigarette lighter, then put the laptop on a bag on the back seat. East he went. Geoff had the night shift on another Internet giant’s campus. This meant he drove a golf cart around once or twice, then parked himself in the camera room and tried not to sleep. Sleeping would cut his hourly wage and get him kicked back to dangerous, dirty jobs like protecting rail yards from motivated thieves. He used to pick a skill and research it. He learned to get basic vocabulary in Spanish, Mandarin, Fujianese and was trying Tagalog. He could carry a conversation as long as it revolved around simple topics, like where the bathroom, parking lot and reception desk were, or that he wanted to purchase something. Tonight he picked at that truck thing again. He used a map application to virtually drive between Phoenix and San Diego. After a few hours, he found the spot on the Interstate that looked like the right landscape from the cameras on the pinball machine. He looked at the street view and the camera view over the older man’s shoulder. Motherfucker. Spot dab in the withdrawn zone. Who travels to the middle of nowhere to steal from a truck and only take some stuff? Couldn’t be locals. Locals would strip the truck bare. He watched the video again. Looks like they took plain grocery shipping boxes. Inside job? And steal boxes of fresh pasta and imported wine? He scrolled back and took a few screengrabs. When he worked security at the shiny new headquarters, they had some wild surveillance tools. Real time tracking using AI image enhancement and they taught you how to use it. Geoff got pretty good at it. He looked over at his phone and opened the scheduling application for his employer. He underbid a few other people and picked up the next shift. Which got him reinstated access to the HQ’s slick surveillance system. He uploaded the images and asked it to clean it up. He expected this to take a bit of time, so he cleaned up and got ready for his shift. And his phone dinged. A match. That he didn’t ask for. Ten seconds later, he saw a corporate ID card. With that bored look of middle aged techie. Falstaff. Huh. Dumb name. Looked familiar, but so did every other techie from where he stood. Probably had more money in options than he’d ever earn. As he drove to work, he wondered why a techie would be robbing trucks in the middle of nowhere instead of getting rich or dying fat here. He parked, took the shuttle and made it a few minutes early for shift change. He expected a slow night. Five minutes into the shift, he was sipping good coffee and watching the camera feeds when someone asked for him by name at the desk. He looked up and saw one of the muscular internal security people smiling at him. Close cropped hair, clear coiled earpiece and the look of someone who worked out at an actual gym instead of lifting five gallon buckets filled with water in a rest stop parking lot. Looked like internal security, maybe even VIP protection. Guy probably had pretty good benefits. Geoff would love to get a job like that. Geoff pushed his coffee to the side and stood up to greet the guy asking about him. Enzokuhle gave Geoff a broad smile and introduced himself as Enzo. The two men were pleasant with one another, but Geoff seemed wary. Enzo didn’t know why he was there either. He was scheduled to do driving and personal protection for a senior exec working in his office, but he got tasked with asking a contract security guard some questions about something very hush-hush. Whatever. He was good with people. Perhaps he’d learn something. “Geoff, may we speak outside? This is a sensitive matter, requiring some discretion” Geoff motioned to his puzzled co-worker by holding up his hand, splaying his fingers and mouthing the word “Five”. The two men walked through the stark but stylish lobby onto a manicured park-like field. “So, what do you want from me? Not too often we get you guys involved” “An hour ago, you performed a lookup for a company employee. Have you been in contact with that employee?” “No. I had an image I wanted processed” There was an uncomfortable silence as the walked. Geoff realized that Enzo was listening to his ear-piece. Enzo was nodding as he listened. “I see. So you haven’t seen this person outside the picture you uploaded” “No, but I have an idea where he might be” Enzokuhle put his hand up. He wanted to end this transaction as quickly as possible. “Thank you. Please do not speak of this to anybody else. Your discretion is most important here. Return to your post and we will contact you if we need more from you”. He pointed Geoff back to the lobby without making eye contact. Galina Ivanova spent a few more minutes talking to Enzo, then thanked him. This was a false lead. AI must be glitchy. No chance that the developer who stole almost a billion dollars was unloading trucks instead of moving that big pile of money somewhere. Any additional time logged to this goose chase would make her metrics worse. She took off her headset and tried to go back go sleep. Geoff sat back in his chair. He remembered a video of a scuba diver diving under a moving container ship, looking up at the moving propeller and how close they almost came to a gruesome death. Why was that guy important enough to throw an alert to internal security? He looked at his phone and the email with Falstaff’s ID photo. He couldn’t do any lookups to see the last time he was in any of the buildings, since that fed into whatever alerts that brought Internal Security down on his head. But he remembered something. Employee parking wasn’t owned by Corporate. It was a separate company, which required him to remind annoyed techies when their photo ID wouldn’t trip the gate when some absent-minded developer forgot their garage access card. Last time this Falstaff guy used the garage was almost two months ago. Such a stereotype. Silver Porsche. Now he knew why the guy looked familiar. He left the day that big brouhaha happened. Rumors flew about the security and custodial staff- some developers stole the next phone design or a treasure trove of celebrity nude photos or something else of value to these people. Anybody too vocal with their opinions got fired and walked out, which Geoff wanted to avoid. Whatever it was, it was valuable and embarrassing. Made sense to go hide in the desert. And he had an idea where Falstaff was. Maybe, if he brought him back, there’d be a big enough reward to let him to leave the Valley and go back to Ohio. Pay off debts and raise his family. It wasn’t like he was making any headway here anyway. He was going on a road trip. Falstaff was driving slower now. He needed better fuel economy and to take the time to scout out his next stop. Some towns had plain dried up and others still too connected. The last place looked promising. The gas station was a weatherbeaten Sinclair, with a repainted dinosaur. They only took cash. The chain restaurant was burned out and there was a motel “a few miles up”. Hank was sleeping, but Falstaff’s laptop dinged with the results of his attempt to crack Tran’s big blob of data. He had passwords for the handful of accounts Tran had dumped on that chip. They weren’t for the financial application he and Tran were working on. Instead, they were for the store’s production environment. He didn’t have a billion dollars in untraceable currency, but he could send almost any consumer good to anybody on the planet and clean up afterwards. He had some investigating to do, and he preferred a cheap motel to do it from rather than his car. He rented a room for a few days from a surprised old man and tried to ignore the curious stares from a few permanent residents of the motel. At least Hank enjoyed exploring the room and this motel would not get the camera friendly festival crowd.
Minimum Viable Issuance - Why Ethereum’s lack of a hard cap on ETH issuance is a good thing.
This post will explain how the argument used by the average Bitcoin maximalist, thinking that they have found Ethereum’s achilles heel when talking about issuance is actually highlighting one of Ethereum’s strong points and one of the main threats to the longevity of the Bitcoin network. So first let’s answer the question which I know many people have about Ethereum:
What is Ethereum’s ETH issuance schedule?
Ethereum has an issuance policy of Minimum Viable Issuance. So what does this mean exactly? It means that the issuance of ETH will be as low as possible while also maintaining a sufficient budget to pay miners (and soon to be stakers) to keep the network secure. For example, if ETH issuance was halved, miners would drop off the network and stop mining as it is no longer profitable for them to mine. As a result, the network would be less secure as it would cost less money for an attacker to control 51% of the hash power and attack the network. This means that the Ethereum community plans to change ETH issuance as time goes on to maintain a reasonable security budget which will keep the network secure but will also keep inflation in check. We have done this twice in the past with EIP-649 and EIP-1234 which reduced block rewards from 5 ETH per block to 3 ETH and from 3 ETH to 2 ETH respectively. I previously made a graph of ETH issuance over time here: https://redd.it/it8ce7 So while Ethereum doesn’t have a strictly defined issuance schedule, the community will reject any proposals which either put the security of the network at risk such as the recent EIP-2878, or we will reject proposals which will lead to excessive network security and therefore an unnecessarily high inflation rate (or we will accept proposals which reduce issuance after price rises and therefore the security budget rises). This means that when Bitcoiners accuse the Ethereum Foundation of being no better than a central bank because they can “print more Ether”, this is completely untrue. Any proposals made by the EF which would increase issuance unnecessarily would be rejected by the community in the same way that a proposal to increase the supply of Bitcoin from 21 million to 22 million would be rejected. There is a social contract around both Bitcoin’s and Ethereum’s issuance schedules. Any networks or proposals which break the social contracts of 21 million Bitcoins and minimal viable issuance of Ether would be a breach of these contracts and the new proposed network would be labeled by the community as illegitimate and the original network would live on.
So why is minimum viable issuance better than a hard cap?
Minimum viable issuance is better than a hard cap because it puts the most important part of the network first - the security. MVI ensures that the Ethereum network will always have a security budget which keeps the cost of a 51% attack impractically high. Bitcoin on the other hand, halves its security budget every 4 years until eventually only the transaction fees pay for network security. This means that every 4 years, the amount of money paying for network security halves until eventually, the value of attacking the network becomes greater than the security budget and someone performs a 51% attack (technically the security budget only halves if terms of BTC not in dollars. However, even if the price of Bitcoin more than doubles in the time that the security budget halves, the ratio of security budget to value secured on the network still halves, doubling the financial viability of performing a network attack). The strategy to pay for the security budget once Bitcoin issuance stops is for transaction fees to secure the network since transaction fees are paid to miners. Not only does this have its own security problems which I won’t detail here, but unless Bitcoin scales on layer 1 (layer 2 scaling solutions have their own security mechanisms separate from L1), then fees would have to cost well in the thousands of dollars to secure a trillion dollar market cap Bitcoin that is secured by nothing but fees. If Bitcoin maximalists want a 10 trillion or 100 trillion dollar market cap then expect fees to go up another 10 or 100 times from there. Ethereum on the other hand, will be able to keep its network secure with approximately 1-2% annual issuance being paid to stakers under ETH 2.0. This is because not all of the network will be staking, so if 33 million of the approximately 110 million Ether in existence stakes under ETH 2.0, then paying this 33 million Ether 6% a year (a very decent yield!) would cost just under 2 million ETH per year which would equate to less than 2% annual ETH inflation. This is also before considering EIP-1559 which will burn a portion of transaction fees which will counter the effect of this inflation and potentially even make ETH deflationary if the sum of all burned transaction fees are greater than the annual inflation. Also, under ETH 2.0, an attacker performing a 51% attack would get his funds slashed (they would lose their funds) if they attack the network, meaning that they can only perform a 51% attack once. However, in Bitcoin, anyone who controls 51% of the mining hash power could perform multiple 51% attacks without losing everything like they could in ETH 2.0. So in conclusion, while Ethereum doesn’t have the guaranteed anti-inflation security of a hard cap, it does have the guarantee of always paying it’s miners (or stakers under ETH 2.0) enough to keep the network secure. In contrast, while Bitcoin’s social contract may guarantee a hard cap of 21 million, it cannot simultaneously guarantee network security in the long run. Eventually, its users will have to decide if they want a secure network with more than 21 million coins or a tax to pay for security or an insecure network with super high fees and a hard cap of 21 million Bitcoin. Disclaimer:The details I covered around 51% attacks and network security are simplified. I am not an expert in this field and things are a lot more nuanced than I laid out in my simplifications above.
https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/220.127.116.11 Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that. Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap. We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout. Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.
Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now. Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER the v11 transition (around Oct 4th) and BEFORE October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date. The transition height is also when the team requirement will be relaxed for the network.
Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.
The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use. There are so many goodies here it is hard to summarize them all. I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures. The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!
Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.
Network magnitude unit pinned to a static value of 0.25
Max research reward allowed per block raised to 16384 GRC (from 12750 GRC)
New CPIDs begin accruing research rewards from the first superblock that contains the CPID instead of from the time of the beacon advertisement
500 GRC research reward limit for a CPID's first stake
6-month expiration for unclaimed rewards
10-block spacing requirement between research reward claims
Rolling 5-day payment-per-day limit
Legacy tolerances for floating-point error and time drift
The need to include a valid copy of a CPID's magnitude in a claim
10-block emission adjustment interval for the magnitude unit
One-time beacon activation requires that participants temporarily change their usernames to a verification code at one whitelisted BOINC project
Verification codes of pending beacons expire after 3 days
Self-service beacon removal
Burn fee for beacon advertisement increased from 0.00001 GRC to 0.5 GRC
Rain addresses derived from beacon keys instead of a default wallet address
Beacon expiration determined as of the current block instead of the previous block
The ability for developers to remove beacons
The ability to sign research reward claims with non-current but unexpired beacons
As a reminder:
Beacons expire after 6 months pass (180 days)
Beacons can be renewed after 5 months pass (150 days)
Renewed beacons must be signed with the same key as the original beacon
Magnitudes less than 1 include two fractional places
Magnitudes greater than or equal to 1 but less than 10 include one fractional place
A valid superblock must match a scraper convergence
Superblock popularity election mechanics
Yes/no/abstain and single-choice response types (no user-facing support yet)
To create a poll, a maximum of 250 UTXOs for a single address must add up to 100000 GRC. These are selected from the largest downwards.
Burn fee for creating polls scaled by the number of UTXOs claimed
50 GRC for a poll contract
0.001 GRC per claimed UTXO
Burn fee for casting votes scaled by the number of UTXOs claimed
0.01 GRC for a vote contract
0.01 GRC to claim magnitude
0.01 GRC per claimed address
0.001 GRC per claimed UTXO
Maximum length of a poll title: 80 characters
Maximum length of a poll question: 100 characters
Maximum length of a poll discussion website URL: 100 characters
Maximum number of poll choices: 20
Maximum length of a poll choice label: 100 characters
Magnitude, CPID count, and participant count poll weight types
The ability for developers to remove polls and votes
[18.104.22.168] 2020-09-03, mandatory, "Fern"
Backport newer uint256 types from Bitcoin #1570 (@cyrossignol)
Implement project level rain for rainbymagnitude #1580 (@jamescowens)
Upgrade utilities (Update checker and snapshot downloadeapplication) #1576 (@iFoggz)
Provide fees collected in the block by the miner #1601 (@iFoggz)
Add support for generating legacy superblocks from scraper stats #1603 (@cyrossignol)
Port of the Bitcoin Logger to Gridcoin #1600 (@jamescowens)
Implement zapwallettxes #1605 (@jamescowens)
Implements a global event filter to suppress help question mark #1609 (@jamescowens)
Add next target difficulty to RPC output #1615 (@cyrossignol)
Add caching for block hashes to CBlock #1624 (@cyrossignol)
Make toolbars and tray icon red for testnet #1637 (@jamescowens)
Add an rpc call convergencereport #1643 (@jamescowens)
Implement newline filter on config file read in #1645 (@jamescowens)
Implement beacon status icon/button #1646 (@jamescowens)
Add gridcointestnet.png #1649 (@caraka)
Add precision to support magnitudes less than 1 #1651 (@cyrossignol)
Replace research accrual calculations with superblock snapshots #1657 (@cyrossignol)
Publish example gridcoinresearch.conf as a md document to the doc directory #1662 (@jamescowens)
Add options checkbox to disable transaction notifications #1666 (@jamescowens)
Add support for self-service beacon deletion #1695 (@cyrossignol)
Add support for type-specific contract fee amounts #1698 (@cyrossignol)
Add verifiedbeaconreport and pendingbeaconreport #1696 (@jamescowens)
Add preliminary testing option for block v11 height on testnet #1706 (@cyrossignol)
Add verified beacons manifest part to superblock validator #1711 (@cyrossignol)
Implement beacon, vote, and superblock display categories/icons in UI transaction model #1717 (@jamescowens)
How to calculate the value of rewards points. Since each rewards program is different, you’re going to have to do the calculations for each credit card you’re considering. To make it as comparable as possible, at least try and narrow your search down to the type of rewards program you want first. For example, if you’re looking for shopping rewards, choose a few shopping rewards credit ... BitcoinRewards finds you discounts and gives you free Bitcoin at more than 1500 online stores. Add to Chrome Chrome Store ... Better than Flybuys, Qantas Points and Velocity. Now I can earn real value with BitcoinRewards. Phil Hunt. Convenient and easy to use, BitcoinRewards just saved me $25 and earned me a sweet 0.0024 BTC. NativeSouls. Love to shop online globally from home, Save money and ... Transfer those rewards to your Bitcoin account using the option found on our payment page. Is there a minimum value to request payment via Bitcoin. Yes, you need to earn at leasty $40.00 at Superpay.me, and then you can request payment via Bitcoin. How quickly do i receive payments via Bitcoin All payment requests are verified for security, and then verified payments are issues within 24 hours ... Rewards Cryptocurrency Loyalty Points Coin Solution Proposed. In 1793, a local merchant decided that in order to get more customers to his store, he would reward patrons for their loyalty. After a few attempts, he came up with copper tokens, which he would give to customers. These tokens could later be redeemed for items within his store. The idea soon spread everywhere, and it is now an ... Bitcoin is only valuable because it's managed by a blockchain, if it ran on the same technology as today's loyalty points it would be worthless. reactions On the other hand, at the time of writing, the value of one Bitcoin had risen from $0.003 in 2010 to $10,109.72 against the U.S. dollar.
Bitcoin Dominance Reversal At Key Level Points To ...
Blockrize Credit Card Company Giving Bitcoin & Ethereum Rewards Instead of Normal CC Rewards Points ... the first credit card with rewards in Bitcoin and Ethereum Sign up with Coinbase for Free to ... how to use your reward points. and get more and more satoshi on roll. The major event is coming….1 year away. In May 2020, the next Bitcoin Halving event takes place! Each prior halving event has pushed Bitcoin’s price to levels never seen before. Could this be ... Bitcoin Halving 2020: History & Price Prediction (A Simple Explanation) - Duration: ... How to increase Reward Points (RP) in freebitco.in in hindi Bitcoin Rocket - Duration: 5:13. Bitcoin ... Bitcoin’s halving is here in just one week, and the first-ever cryptocurrency is widely expected to rally as a result. But Bitcoin dominance has been consoli...