February 2016

Weekly Updates

Last Week

Happy Leap Year ReddHeads

So, I have now switched across to writing this weekly post and posting on Monday (for me). The premise to this is that the week really ends on Sunday in my world, and usually I get a few points on the board during the weekend (family activities permitting).

It also allows me to recap the week in full, and start the week with a summary of what we have achieved thus far.

So on the surface, it may appear to you that things are still moving slowly (I havent yet made a full release of the new wallet), and the Redd-ID system is now starting to come into discussion. Hopefully you can appreciate that such thoughts couldnt be further from the truth.

New Wallet – RC1 development update

Progress is continuing on the new wallet. Thanks particularly to Didi, who has gone and done remarkable things. In essense he has created a test environment for almost all scenarios with the following considered

  • Windows XP Pro SP3 32bit
  • Windows Vista Home Basic 32bit
  • Windows 7 Home Premium 32bit
  • Windows 7 Ultimate 64bit
  • Windows 8.1 Home 64bit
  • Windows 10 Home 64bit
  • Ubuntu 14.04 LTS 64bit
  • MacOS X Yosemite 10.10.1
  • Debian Wheezy

From that, we have 4 primary issues identified, and in the order of severity

1. transaction fee calculation needs checking
2. Block nVersion validation missing from AcceptBlock()
3. Enable staking after unlocking wallet
4. Rejected stakes stay at the top of the recent transactions list

There is not too much work in resolving these, so should start to get back onto my activity list.

Keep the requests for testing coming in, if your technically minded but not sure where you can assist, you can help contribute by testing the core wallet.

Henry has also offered to put a bit of time into helping with documentation, which takes a load off thinking about this aspect :)

Reddit & Twitter tipbot platform

As mentioned last week, I will be taking active control of the server.

I can confirm the transfer has now been completed and took place on Sunday with an unscheduled outage. Everything is now up and running. Keep on tipping.

Please let me know if you are having problems.


For the Redd-ID system, there are 3 principle parts.

1. Reddcoind
2. ReddID Service and resolver
3. Client Interface

1. Reddcoind

With the new Reddcoin v2.0 wallet software, we are now able to write OP_RETURN data directly onto the blockchain. This allows for a maximum of 80bytes of payload in which to embed various ID related metadata (and some other functionality to be announced later). This will become the cornerstone for many other services into the future.

2. ReddID service and Resolver

As mentioned last week, the goal is to provide both a user level ID system and a networkID level and these will work hand in hand to provide a flexible naming and ID system within the network. Last week I shared a little of the output of the console as to some of the data being pushed. The service component will handle all the backend mapping of hashes and IDs and distributing to other service nodes. The service reads from, and writes to the blockchain necessary OP_RETURN data.

The resolver is a read-only lookup service providing fast resolution of requested IDs, and underlaying metadata. The goal here is that you can enter in a userid instead of reddcoin address, and the wallet will be given the associated address.

3. Client Interface

The new activity from this week has been bringing some of the functionality that was being done in a cli across to a more intuitive GUI. I feel the most logical place to do this is by resurrecting the ‘old’ browser wallet (Do you remember this from this time last year??) and embedding the ReddID functionality. Later this will also be included into the electrum wallet and the QT wallet

While we are discussing this, there were a few issues with the old browser wallet previously, so I would be interested to hear from anyone who may still be running the old code. Suffice to say, as one of my many tasks, I am also in the process of putting to bed some of those outstanding issues and bring in the new functionality for the ID system.

Browser Wallet Eye Candy:

[Start Screen](https://i.imgur.com/9TDGkaX.png)

[Create ID](https://i.imgur.com/MjgtYV9.png)

In Closing

So starts a new week, I will be focusing more time on the listed QT wallet issues and hopefully have them sorted in time for the next update.

Keep on staking!


X-Posted [https://www.reddcointalk.org/topic/775/state-of-the-redd-nation-feb-29-2016](https://www.reddcointalk.org/topic/775/state-of-the-redd-nation-feb-29-2016)

Weekly Updates

Last Week

I dont know about you, but I have had a fantastic week.

I will start by saying, what I was really excited about was that I able to make some great inroads into the ID development early in the week and everything technically is starting to come together. I am not going to pretend, there is still quite a ways to go before even close to public testing but I consider a major milestone has been met.

One of the things that constantly becomes a challenge is not to stray too far from the tasks. Essentially, it is about goal setting, and trying to reach those goals. Make them achievable enough that they are not missed, why challenging enough to keep extending yourself. Only after the task is met do I let some distraction then turn my attention.

I think 2016 is going to be a bit of a turning point in the crypto space. There seems to be some broad consolidation of thinking on blockchains, and that they hold some secret power. IBM, Microsoft, just about everyone is getting on board. Over all, it is going to be an interesting space to watch. What is unfortunate is that all these companies do it in denial of Bitcoin, which brought the technology to the masses.

Despite this acceptance, I think it is still a bit of a Red pill/ Blue pill moment.

Bitcoin was born not to solve a problem with banking. Banks will always be banks. Their acceptance of blockchain technology is not to make transactions faster and cheaper for you, but rather faster and cheaper for them. PROFIT and BOTTOM LINE improvements. Bitcoin (and of course Reddcoin) is able to introduce an electronic peer to peer (person A to person B) system to allow the transfer of your funds without going through a financial institution. A system that is better for us

“You take the blue pill, the story ends.
You wake up in your bed and believe whatever you want to believe.
You take the red pill, you stay in Wonderland, and I show you how deep the rabbit hole goes.”

―Morpheus, to Neo
If you have not ever read the whitepaper [Bitcoin: A Peer to Peer Electronic Cash System :: Satoshi Nakamoto](https://bitcoin.org/bitcoin.pdf) I do suggest you take a read.

New Wallet – RC1 development update

I have now had a few more people asking to test out the new wallet which is fantastic. Thankyou for all the requests.

A special shout out to @Didi who has taken it upon himself to create EVERY test environment: talk about going above and beyond. Didi, for you who dont know has kindly been creating a blockchain snapshot to help with bootstrapping process.

I was hoping to get another build out this weekend (RC2??) containing the few gramatic and spelling errors which I have picked up, however, I have uncovered a real bug that needs deeper attention. The fee calculation on some transactions is much higher than expected when using the GUI. This is not always evident for every transaction, but when it is, it can be as much as 5000RDD in transaction fee. OUCH!!

I need to get on top of this issue before making good on the more broad invitation so that there is no risk to your funds (this is a technical release to be run on Testnet, however, I also want to avoid the temptation to run on mainnet). As this is a problem with fees, it would be included to anyone staking the block contating the fee (lucky for the one staking the block). Suffice to say, ideally this needs to be fixed before the wallet is put further into the wild

In light of this, the wallet otherwise is behaving as it needs to be in terms of testing and running on testnet. I will be focussing on the next phase of Reddcoin before switching back to track this particular issue down unless it becomes a deeper operational issue.

Please be patient, as I feel the next phase will be worth the wait.

Current Reddit tip platform

Recently it was brought to my attention that the tipbot on Reddit wasnt working so well.

In an effort to get things working again I reached out to Jonathan to check on what might be the problem.

After a bit of a conversation, we have both agreed the best course of action will be to transfer the server image running the tipbot across to myself. Please be patient whilst this activity is undertaken, I will provide an update when completed and everything in order.

Ultimately this is an interim solution and personally I dont like all the responsibility on my shoulders. However, the end game plan here is to get to a decentralised platform where we are not relying on central administration.

Thanks Jonathan for allowing this action to take place.

More on Cryptsy Withdrawals.

More of a RFI, but curious if anyone has successfully withdrawn their funds from cryptsy in the last week or so?


Any delay in fixing the above mentioned wallet transaction fee issue is directly related to this baby.

I have to say that a lot of progress was made this week, so I wanted to keep my focus whilst the grey matter is pumping and I am on a roll.

There is nothing too exciting to show, it is a console based server. But maybe a screen grab might be exciting to some of you.

The above is running on the Reddcoin testnet.

The namespace_id refers to the root identity on the blockchain, the Network ID (NID). ‘Blog’ was a name that i was testing with.

On the blockchain, multiple NetworkIDs can exist. Think of these a bit like domain names, or comapany names, or group names. Users when they sign up for an ID, will subscribe to a particular (NID).

e.g ‘john.blog’ or ‘gnasher.reddcoin’

The NID names might be a generic, or they will be a more specific NIDs reflecting for example a company. NIDs can also be public idenities, while others private in nature.

So whilst I was revelling in this moment and pondering, so many other possibilities came to mind as to how the embedding of data in the blockchain could be used. What makes this exciting is,

  • Reddcoin has a 1min blocktime
  • The available space to store data is 80bytes
  • multiple transactions can be embedded into a single block
  • The one staking the block not only gets the stake reward, but also gets the transaction fees of all the included transactions in the block.
  • Reddcoin is currently at about 1% block capacity

Please feel free to discuss if you would like more.

In Closing

Again, thankyou for taking the time to read Redd-Nation,

Just an FYI, I am also going to switch the publishing date to be a Monday (for me that is). Friday is just way too hectic a day to focus on pushing these weekly updates out.


Weekly Updates

Last Week

Another week has rolled by. So where did that week go, it seems like only yesterday that I wrote the last update. Maybe it has something to do with my age, as the time feels like only half of what it should have been.

Behind the scenes there is a lot going on and never a dull moment doing development. Sometimes it is difficult to convey all the activity that takes place. Think of it a bit like a lava flow… on the surface it moves steadily across the landscape, but under the surface it is a rolling and boiling entity.

So in the last week, the new wallet release candidate has been running very well, with not too much to report. Some typos and and such here and there that need to be rolled into the next build.

New Wallet – RC1

The new wallet is looking very promising. The changes to implement based on Bitcoin Core seem to have been well incorporated. The recent fixes are none critical and cosmetic, and will be rolled into the next build (RC2).

I have started putting release notes in order and general document tidy up. This part is quite time consuming as i need to cross reference multiple software packages.

I think we can start looking to a larger test environment, with potential to release onto mainnet in the not too distant future. I have a few migration tests to do first.

Cryptsy Withdrawals.

And for some more good news, thanks for @bitnation for checking in on current Cryptsy withdrawal status.

It would seem that withdrawals have been enabled now for Reddcoin.

If you havent already, and you want to keep your coins, now is the time to get them off the exchange and into your own wallet.

Please note that Cryptsy also have a phishing attack of users to try and havest username/passwords. They have reset all passwords so you will need to re-establish

Collaborative Discussions

I have mentioned in the past that I believe we can operate in a competive, but collaborative market space. Particularly in the scope of altcoins. Whilst ever we operate in a divided (them/us) scenario, we will have a tough battle to succeed. A lot of lessons can be learnt by sharing experiences on what works and what does not.

A couple of examples I would like to mention are /u/Prohashing made a reference in his posting Progress and lessons learned from implementing BIP101 on altcoins. Steve has been doing some great work in porting BIP101 not only to litecoin, but also sharing his knowledge so that other devs can take advantage. A very interesting read if you have the time

Also /u/rnicolls of Dogecoin, has a lot to offer the community with his extensive experience and he has been active on a number of forums.

I am heartened to see such discussions happen outside of their own core work.


I want to start introducing discussion about the proposed ID system and what you can expect.
This has always been one of the main visions for Reddcoin, and a key feature for being able to make a successful social tipping platform.

Our goal is to provide a service that is both easy to access, and will provide added value.

Since early last year I have been looking various systems that have been implemented and how successful they have been, and what features they contain. This extends from embedded blockchain solutions like Namecoin, to products like keybase and Blockstack (formally OneName). Considering the options available, and based on my other RL experience, I am working on a solution that incorporates a combination of data embedded in the blockchain, and off chain storage.

The advantage is that it allows for extended data storage and manipulation. The on chain storage uses the OP_RETURN function and has an 80Byte capacity and the off chain storage is made up of DHT (Distributed Hash Table).

In essense, and if you are familiar with them, I have borrowed a lot from OneName/Blockstack as I think they have a very workable solution that can be adapted to what we are trying to achieve.

One of the other reasons for selecting this approach is that helps to seperate into layers the various services of the network.

I have been working on porting this into Reddcoin for the last few months (while taking a break from the Core Wallet). I am not putting a time frame yet, as there is still quite a ways to go.

But I would like to share some of the features that will be available:

  • Capability of registering a unique UserID (UID)
  • Capability of registering a unique NetworkID (UID)
  • There is an algorithmic generation of the fee based on complexity
  • Active wallets will have the opportunity to stake the UID/NID generated fee (on top of staking fee).
  • Name lookup embedded into Reddcoin-QT, Electrum Wallet, Browser Wallet

In the coming weeks, I will share more of what is install

In Closing

Thanks for taking the time to read Redd-Nation,

This coming week is already shaping up to be quite busy. Most of my focus is now on getting stuck into ReddID and making it reality for all of us.