Issue 62 of Politeia Digest is online now!

Three new proposals this time, about rebranding @decredmagazine, making promotional videos, and making a website showcasing DCRDEX - these and the Decred.club proposal are all ready to start voting!

blockcommons.red/politeia-diges…

Issue 61 of Politeia Digest is online now!

One new proposal this time, to fund the development and maintenance of the Decred.club website.

blockcommons.red/politeia-diges…

New issue of Politeia Digest is out now. It features the proposal to upgrade decred.org with new images and copy, which is currently being voted on.

blockcommons.red/politeia-diges…

New issue of Politeia Digest is out now!

Two new proposals this time, both renewals of established projects. @DecredDEX is up for its 3rd phase with a major release ready to roll, while the @StakeShuffle_ twitter bot is wrapping up phase 2.

blockcommons.red/politeia-diges…

New issue of Politeia Digest is out now!

Two new proposals this month, one to change the block reward distribution so that PoW miners get a reduced share, and the other one is for a renewal of the @DecredArabia content and events program.

blockcommons.red/politeia-diges…

New issue of Politeia Digest is out now! One new proposal this month from @Ammarooni, a program of economic education and outreach, and it's ready to start voting!

blockcommons.red/politeia-diges…

New issue of Politeia Digest is out now!

There are two new proposals this time, both from @raedahgroup: to fund continued work on the GoDCR wallet (using and sponsoring @giouiorg), and the Android and iOS mobile wallets.

blockcommons.red/politeia-diges…

New issue of Politeia Digest is out!

Two new proposals are ready to start voting. The first is from @LindseyMelissaM to renew Monde PR's efforts for another year. The second is from @Finstreet1 to make a series of educational videos in the Hindi language.
blockcommons.red/politeia-diges…

New issue of Politeia Digest is out!

Two new proposals this time, a crypto conference and a sci-fi miniseries! @DominicFrisby's documentary proposal is still racking up comments (103) and versions (25) too, with a new interview and taster added recently.

blockcommons.red/politeia-diges…

New issue of Politeia Digest is out!

3 new proposals since last time. 2 are already voting strongly (Automatic Ticket Revocations and @StakeShuffle_ ), with an in depth discussion taking place on the 3rd about spending $300K to fund a documentary.

blockcommons.red/politeia-diges…

New issue of Politeia Digest is out now!

Three new proposals are under discussion and will soon start voting: Bug Bounty phase 4, Translations phase 2, and a new consensus rule change proposal for explicit version upgrades.

blockcommons.red/politeia-diges…

New issue of Politeia Digest is out now!

Politeia is back with the deployment of v1.0.0, which adds a snazzy new backend and sets the stage for exciting developments. The first proposal to be discussed on the upgraded Pi is for its further development.

blockcommons.red/politeia-diges…

New issue of Politeia Digest is out now, covering the last 7 weeks of Decred Pi action. It has been a fairly quiet time, with 3 proposals approved, 1 rejected, and 1 still open for voting.

blockcommons.red/politeia-diges…

One of the new variables for this year: fixed cost or pro rata costing. Proposals that bill on an hourly pro rata basis do better than those which have a set cost for delivery or a cost per unit for set number of units.

All of the year 2 proposals which went to a vote, point size reflects requested budget size.

Proposals by domain (manually classified by me), with colors reflecting proposal's state at time of writing.

The approval rates of proposals are generally lower than in year 1. Mean approval % for year 2 proposals that pass was 78.7%, in year 1 this was 85.9%. Mean approval % for rejected year 2 proposals was 20.6%, in year 1 this was 24.2%. 66% Yes votes year 1 vs 54% Yes in year 2.

Mean voter turnout was 27.9%. This year saw the first proposals failing to meet the quorum requirement, with 3 proposals failing to reach the required 20% voter participation. The highest turnout (41%) was for the Latam 2 proposal, which narrowly passed (60.7% approval).

It's two years today since Decred's Politeia launched, and this new post from @RichardRed0x gives an overview of proposal activity metrics for the second year.

blockcommons.red/publication/po…

Some graphs below:

Issue 38 of Politeia Digest is out now!

The 4 RFP proposals with competing visions of the decred.org messaging are live and voting, and summarized within. There's also a new proposal to fund community translation efforts.

blockcommons.red/politeia-diges…

Issue 37 of Politeia Digest is out now, covering the last 2 weeks. There are 2 new proposals which have already started voting, and a further 4 proposals responding to the decred.org messaging RFP - still under discussion and community review.
blockcommons.red/politeia-diges…

The latest post on blockcommons.red is more interactive than usual, it's a thought experiment and survey from @RichardRed0x.

What's up with those Youth Booster Credits? A light-hearted 10 minutes that's fun for the whole family.
blockcommons.red/post/youth-boo…
*fun is subjective

Issue #36 of Politeia Digest is out now!

It's a short one, with just two new proposals to consider: Phase 2 of @coveryfire7777's video production proposal, and an RFP proposal to change the messaging on decred.org.

blockcommons.red/politeia-diges…

Issue #35 of Politeia Digest is out now, covering the last two weeks on Decred's governance platform.

Just one new proposal this time, from the contractors who work in the design sub-domain, and it's already voting!

blockcommons.red/politeia-diges…

Issue 34 of Politeia Digest is out now!

5 new proposals this time, each seeking a piece of the Decred Treasury pie to fund moderation or outreach activities (from poker tournaments to travel booking sites to influencer campaigns to memes for hire).

blockcommons.red/politeia-diges…

Issue 33 of Politeia Digest is out now!

It's been a quiet month since the last issue, with just 3 new proposals published. Proposals currently under discussion concern Public Relations and Augmented Reality posters.

blockcommons.red/politeia-diges…

The post concludes with comparisons to how two similar inflation bugs were handled in Bitcoin's history. One was exploited and the chain rolled back, but this was before Bitcoin was a big deal. The other was fixed quietly in 2018 before being disclosed, it was not exploited.

Now the question is what to do about those extra 298 million RVN, how to incorporate them into the planned issuance schedule which the network's participants thought they had agreed to as a foundational principle of the network.

Expected to see something about being more careful with pull requests from accounts with no history here.

I'm also surprised how stable the price of RVN was while all of this was going on. With the new attackers burning much of the new RVN they created while the fix was being deployed, it probably worked out as well as anyone in the RavenCoin community could have hoped for.

Messages from @tronblack at the time indicated that law enforcement had been contacted. This writeup reflects that probably no laws were broken by any attacker here, but concludes that it was right to raise this threat in communications, to incentivise cessation and burning RVN.

A RavenCoin community member uncovers information that allows for one of these new attackers to be identified. This attacker subsequently burns the RVN they minted.

The initial attacker's transactions stop, but two new attackers appear, they seem to have identified the exploit from information that had been included in the post about it. Two million RVN is created by these attackers.

After known miners and exchanges had been forewarned, the code and first blog post about the issue was released. This was obviously an intense time for the developers, with someone watching to see what the attacker would do in response.

Something that grates in the write-up is the idea that RavenCoin is more decentralized because more of its hashpower is coming from unknown sources. Looking at the % of the hashpower which you don't have contact details for is not a good measure of decentralization.

The patch was deployed using BIP 9 method, so would gauge support over a 2016 block interval - in RavenCoin's case blocks are 1 minute apart. There was a race to reach the 70% mining adoption threshold for activation within the first 1.4 day cycle.

The attacker was able to create RVN at will, so once they realized their golden goose was being slain they could burn down the ledger if they chose to by minting silly amounts. Devs put out a decoy change to the public code, giving miners access to a private repo.

Once this was reported to @tronblack and team they set about coding a fix. The fix was not itself difficult and could be done as a soft fork, so only requiring adoption from PoW miners to activate and secure the network against further attacks.

The exploit was discovered by the cryptoscope.io block explorer team. They have done the @RavenCoin community a great service, probably saved the whole project, by identifying this problem while the damage was limited to ~4% of the circulating RVN being illegitimate.

The attacker was minting 500,000 RVN every two hours since May 9, and it was moving in recognizable patterns, probably automated, to an exchange address thought to be controlled by Binance.

Maybe it's just the benefit of hindsight, but this looks like a fairly suspicious account to be entertaining pull requests from, especially if they touch on the enforcement of consensus rules in any way.

This is thought to be a deliberate attack because it's the only contribution that GitHub account made (to anything, see their GitHub profile: github.com/WindowsCryptoD…).

The attack was enabled by dropping a check that should have been made on certain types of transaction, that no RVN outputs were being created, because those transactions had no business creating RVN outputs. A broad check was replaced with 2 narrow checks, should have been 3.

It seems one of the perpetrators left a trail, and the post encourages them to consider burning their ill-gotten RVN in order to enjoy a more guilt-free life.

The recent #Ravencoin inflation bug is a reminder that cryptoasset networks are constantly under scrutiny for weaknesses by people looking to exploit them and their users. Protocol bugs affect all users by debasing the blockchain's native assets.

medium.com/@tronblack/rav…

Issue 32 of Politeia Digest is out now!

Two new proposals this time, Bounty Phase 3 is ready to start voting while Planet Decred (the proposal) has already been abandoned, with some parts launching immediately and others to return in their own proposal.

blockcommons.red/politeia-diges…

Four Decred Politeia proposals just went up for stakeholder voting. If you have live tickets, this (next week) is the time. 🎫🎟️💸

There are summaries in the last issue of Politeia Digest: blockcommons.red/politeia-diges…

and in video by @coveryfire7777: youtube.com/watch?v=9i56ly…

This one shows volume of DCR being traded per day. There has been surprisingly little impact of the MM withdrawing orders.

The Huobi data feed went bad around May 10 so it has been excluded from that date onward. May 1-10 everything looks about the same as it has been.

Same for the USD markets.

Bittrex USD order books flatlining, but there's some life in Huobi.

BTC markets order books at up to 5% from current price.
The MM finished up on April 30th, you can see their orders disappearing pretty clearly.
Binance looking lively enough on the buy side.

Politeia Digest #31 is out!

5 new proposals have come in over the last 10 days. We've got on chain research and charting site proposals, marketing in Latam, marketing on TV, and sponsoring a book - Decred stakeholders will be voting on these soon.

blockcommons.red/politeia-diges…