The latest Ravencoin update is now available at https://github.com/RavenProject/Ravencoin/releases.  You can also find it by going to Ravencoin.com or Ravencoin.org and selecting the "Wallets" option at the top of the page of the former, or the "Download Binaries button on the main page of the latter. 

This update adds a hotfix for a bug that was inherited from bitcoin which allows double spend attacks using the chain.  It is highly recommended that everyone update their wallets as soon as possible in order to help prevent these types of malicious attacks.

This is just a friendly reminder about the open developer meeting being held today in the IRC chat (freenode network) today at 4:00 pm EDT / 8:00 pm UTC.  It will be in the #ravencoin-dev channel.  You can also view the live feed of the discussion in the Ravencoin Community discord #irc-ravencoin-dev channel.

Ravencoin.com has had a recent face lift, and it's looking sharp!  Additionally, it is now built with static HTML, so anyone with web dev experience or ideas can submit PR's for the website through the github at https://github.com/RavenProject/ravenproject.github.io

Tron just published “Ravencoin — Asset Issuance Cost” https://medium.com/@tronblack/ravencoin-asset-issuance-cost-52b553c507cb … $RVN @Ravencoin #Ravencoin

For those of us interested in hardware wallets, Ledger now has Raven on their trello board for implementation.  There is also an option to leave a vote, so head on over and show your support!
https://trello.com/c/zWMOxADR/86-ravencoin-support#

Hi all! The android wallet update post-DGW is available.
https://play.google.com/store/apps/details?id=com.ravencoin

Ravencoindev made a tweet yesterday that shows the effects of pre- and post-DGW stats.  It's pretty cool to see them side by side.
https://twitter.com/ravencoindev

Yes, an iOS app is in development, and should be ready soon.

Today's open developer meeting will be held in IRC #ravencoin-dev at 8:00pm UTC (4:00pm EDT).  The meeting will post (read only) in real time to the Ravencoin Community discord server's #irc-ravencoin-dev channel.

Hello!

The Ravencoin v2.0.4 wallet binaries are now available and can be downloaded at https://github.com/RavenProject/Ravencoin/releases/tag/v2.0.4

This update will enable the Dark Gravity Wave difficulty adjustment for mining, contains the code for the asset layer that will begin activation on October 31st, and it fixes a few bugs found after v2.0.3 was released.

*IMPORTANT!* The DGW adjustment will activate on block 338778, which will result in a hard-fork of the ravencoin chain. Please apply the v2.0.4 binary updates as soon as possible in order to ensure that your wallets are on the correct chain after the fork. Anyone not using the new software upon the activation at block 338778 will be "forked off" and will remain on the counterfeit blockchain.

Common Questions:
What do I need to do to update my wallet?
Step 1. Backup the old wallet so you will have a backed up .dat file
Step 2. Download the new wallet (see the link above)
Step 3. Extract/Install the new raven-qt
Step 4. Run raven-qt and verify that you are syncing correctly to the blockchain.
* If you are not able to see your coins, import that backed up .dat file into the wallet.
If you need additional support go to #wallet-support channel of the Ravencoin Community discord server.

Do I need to update my paper wallet(s)?
No. You control the keys to your funds with a paperwallet, which you will import to an updated wallet when you decide to access the funds.

What will happen if I don't update?
If you don't update your wallet it will remain on the old chain, and any coins on that wallet will not be accessible on the new chain.  The coins will not be lost, but you will not be able to access them on the new chain until you update the wallet.

How does this affect people who are mining?
If you are mining via a mining pool, it will not affect your abililty to mine because the updates will be done on the pool side. However, if your mining payouts are going to an old wallet, you will not be able to access them on the new chain until you update that wallet.

What if I have already updated to v2.0.3?
If you have already updated to v2.0.3 and you can see your coins after syncing to the blockchain then you will not need to update again.  (though it wouldnt hurt).  If you are experiencing issue when attempting to sync to the blockchain or when activating the QT client, you will need to update.

Everyone who wants to be able to access their coins will need to update.  Things like paper wallets won't be affected because the keys will be restored to an updated wallet when the holder wants access to them.  If you don't update your wallet you won't lose your coins, but you won't be able to access them on the correct chain until you do update.

The v2.0.3 binaries are available to download on the ravencoin github.  Assuming that everything continues to run smoothly, and no significant bugs need to be addressed, this is the version that will activate DGW and BIP9/RIP2 consensus voting for the asset layer.  Everyone will need to update to this version soon (before block 338778), with a particular emphasis toward pool owners and exchanges, as it will result in a hard-fork of the Ravencoin chain.  I'll reach out to those people at the end of the day since the devs want to do a bit more testing.

https://github.com/RavenProject/Ravencoin/releases/tag/v2.0.3

Hi everyone.  The developers are going to start doing a 1 hour open dev meeting every week (or every 2 weeks - details are still pending) on IRC.  Everyone is welcome to attend, but for the sake of staying on target, please limit interactions to questions and comments on code or projects that you are working on.  Any time left over at the end can be opened up for general Q&A.  The channel is #ravencoin-dev on https://webchat.freenode.net/

Today's meeting will be held at 2:00pm MDT (8:00pm UTC).

This is being investigated by the devs, and more info on a solution should be available soon.

For those of you interested in attending the Ravencoin meetup in October, you can find information here:
https://www.reddit.com/r/Ravencoin/comments/93ijpc/first_annual_ravencoin_meeting_portsmouth_nh/

Yes.  The binaries for the asset layer will be available on July 30th so that people can begin testing it on testnet.  There is not an explanation or walk-through yet because some things could possibly change during testing, but there will likely be educational resources by the time assets are released on mainnet, which is set now for October 31st.

The short version is that the binaries for the asset layer will be ready to download and test on testnet on July30th, and there is a tentative date set for mainnet asset layer release on Oct 31st.

For those who may not be aware, we now have a declaration memo that was written by a couple of lawyers in the community, which can be supplied to exchanges that request such a document.  There is a wiki page with a link to the doc, which you can find here: https://raven.wiki/wiki/Legal_discussion

There was a discussion on ravencointalk.org a couple months back about the cost of burning RVN for assets.  Different ideas were pitched, but all of them had flaws that eventually came back to 500 RVN being the best option.  The cost to create assets should not be minimal as it directly affects the token economics of the coin.  If (when?) raven becomes widely successful, and the value of the coin makes a 500 RVN burn amount cost prohibitive, the burn price can then be reevaluated and adjusted accordingly. The $1 price point has been discussed internally quite a bit, and $500 to create an asset is very reasonable considering who will be creating assets at that point, and what they will be used for.

You can read more on this discussion at https://www.ravencointalk.org/post/discussion-on-the-rvn-cost-to-create-assets-9735335?&trail=10.
Page 4 is where Tron addresses many of the comments and the reasoning behind the current burn amount.

If anyone is interested in a more detailed synopsis of testnet/mainnet activation, you can check out a google doc written by Tron here:

https://docs.google.com/document/d/1RxRokp_P9Iu7eqKdfR7wj2D7bqMwqnd_l3R1yjq633k/edit

He is also going to put it in the github for future reference.