Let's say we are trying to create a WIN-WIN-Situation. It's not WIN-LOSE:

We shall see about that competition.... by the time it's ready you will not crave for BTC anymore, my friend.  

Don't forget to check out the in-wallet vanity address generator.

 

I did a little github house cleaning.

all of mr.spreads original branches (master, mn-test and cpuminer1.2) are now in their own repository called mrspread:

https://github.com/spreadcoin/mrspread

And the main repository spreadcoin https://github.com/spreadcoin/spreadcoin
contains now only a branch called master and one called newwallet.

master will always be the most uptodate and well tested version of spreadcoin.
newwallet will always be the current beta wallet where new wallet functions will be introduced and tried out over time.

Eventually after a while, newwallet will merge to become the new master, as has just happened now.
That's why master and newwallet at the moment are identical, because we just had the new release, but I will start working on new wallet-features right away (there is always something to be fixed, improved or introduced),
so if you want to test new wallet features always look into newwallet branch.

Thanks, and stay tuned.

No, we still use the same protocol as always, no new hardfork has happened since mr. spread left, just the wallet has been given a facelift.

You will be informed here early enough when a hardfork is exactly going to happen.

No worries!

Just stay tuned and follow us here and in the forum: http://www.spreadcointalk.org

Exactly. Reduction of both blockreward and blocktime by a factor of 10 so to speak.

But what I don't get is.... if the first Hardfork happened at exactly after the block 2200 ....

{

as can be seen in the code: https://github.com/spreadcoin/spreadcoin/blob/master/src/main.cpp#L96 getFirstHardforkBlock() is defined as 2200.

And we change the protocol behaviour according to if we are greater than > getFirstHardforkBlock(), for example see here:
 https://github.com/spreadcoin/spreadcoin/blob/master/src/main.cpp#L1343

}

... then why did it take until block 2202 to come into full effect?  

What caused that behaviour?

See blockexplorer (block 2200) : https://chainz.cryptoid.info/spr/block.dws?2200.htm
See blockexplorer (block 2201) : https://chainz.cryptoid.info/spr/block.dws?2201.htm ----> Blockreward still 66
See blockexplorer (block 2202) : https://chainz.cryptoid.info/spr/block.dws?2202.htm ----> Finally!

Can someone explain why this can happen?
Why didn't it change at block 2201?

After all the second Hardfork happened exactly after the defined block 43000. So why was the first hardfork off by a block?

I fixed it.

Sorry for the inconvenience.

I switched from .7z to .zip and forgot to update.

 

BTW, I am working on a block-explorer visualization tool
that helps me (and everyone interested) to look thru all the hex-code-jungle and get a better grasp of all the information within the blockchain.
That's what it looks like at the moment:

This is block 43000, right before the second HardFork happened, back in sep 11th 2014:



And this is the next block 43001 with 2 new fields introduced for solo-mining enforcement: hashWholeBlock and MiningSignature:



I still need to decipher all transactions and their inputs/hashes and script codes...

I just learned that stonehedge will do the weekly update tomorrow.

His weekend started a little early, ... 

Thanks.

I couldn't stand the old crude design anymore that is still used by hundreds of coins.

So I had to do something to not get eye cancer!  

   

You are welcome....

hey we haven't even started yet.

Stay tuned!

Yep, and all CAPITAL LETTERS!

Thanks for checking mac version.

Ok, I say it's a wrap.

On to the next thing on the to-do-list.

Awesome, thanks for testing.

Oil those vocal chords, eightspace, we are going to need many more tutorials soon!

Thanks alot. I am highly motivated and momentum is here.

Currently I am working on slightly improving the website, I need a place to show "News" and "Blogposts"...

what good is a website without news-section, lol.

It will look something like this:



There will be a news-reel that leads to a wordpress powered blog.

I should have it finished in a day or two, so that future news are better handled.

Alright.

All builds are finished.

New official Version is now 0.9.16.1

I replaced the old links with the new ones, so just use the official download links to get the newest wallet-versions (and daemons):

http://www.spreadcoin.info/downloads.php

List of new features/updates:

- Better implementation of Fallbacknodes (react quicker, and more of them available), so you'll probably never need to addNode in conf file ever again.
- Better control of vanitygen (you can use DELETE-Key to erase VanGen-Patterns you don't need anymore and RETURN key to add a VanGen-Pattern, meaning you don't need to click "add pattern" anymore while you type, this makes adding many patterns very easy.)
- Version Nr is now visible in splashscreen and header.
- removed a few layout bugs (depending on what linux system you used (KDE, GNOME) it had problems showing the nativeMenu-Bar (or the menubar within the window) correctly).
- minor improvements and removements of old unneeded stuff.

Let me know if everything works.

Thanks, and stay tuned for more.

PS Donations are highly welcomed.

Alright, new version has been given.

https://github.com/spreadcoin/spreadcoin/commit/6a08477a8dcf361b7580d68b0426e5fa5e5d1c00

Plus splashscreen and header (under the logo) will now show the version nr.





so when someone asks you what version you have running, you can answer immediately.

Thanks.

I am doing a few small improvements before I'll make the final builds.

You can follow it here:

https://github.com/spreadcoin/spreadcoin/commits/newwallet

Also: I will give this Version a new Number:

CLIENT_VERSION_MAJOR       0
CLIENT_VERSION_MINOR       9
CLIENT_VERSION_REVISION    16
CLIENT_VERSION_BUILD       1

I decided to move up a whole Revision Nr, since the wallet now looks and behaves so completely different than before.
We can count a few build-versions up from here, and make the first working ServiceNode-Iteration a Revision Nr. 17 when we are ready...

Stay tuned.

Over the weekend I created new builds for all systems.
I will replace the old wallet with the new one now.

Stay tuned.