Topic: [SDC] ShadowCash | Welcome to the UMBRA - page 253. (Read 1289707 times)
i believe it will be a hard fork so no scrypt after that.
Update: Tuesday, 20 April 2015
New ShadowCore Client Now Available For Public Testing
Our development team has been hard at work integrating new features into ShadowCore that will better support our upcoming ShadowMarket. In order to best support a P2P marketplace environment the ShadowCore client has been updated to prepare the network to switch from using Proof of Stake to Proof of Stake v2. PoS v2’s revised coin weight calculation encourages greater network stability by not factoring in “coin age”. Therefore saving up coin age is no longer possible so nodes will need to be online more in order to get their stake reward. It'll involve a move from scrypt to SHA256 which will mean staking requires less processing power (especially helpful for mobile users wishing to stake their coins). The new system is also designed to solve security issues which made PoS v1 coins open to certain theoretical attacks. For more information see Blackcoin's Proof-of-Stake Protocol v2 white paper.
Great news, thanks!
So how will some wallets using SHA-256 while some others are using Scrypt on the same blockchain affect things? It seems to me like the two algorithms would be at war with one another, with one not accepting the solved blocks of the other.
Update: Tuesday, 20 April 2015
New ShadowCore Client Now Available For Public Testing
Our development team has been hard at work integrating new features into ShadowCore that will better support our upcoming ShadowMarket. In order to best support a P2P marketplace environment the ShadowCore client has been updated to prepare the network to switch from using Proof of Stake to Proof of Stake v2. PoS v2’s revised coin weight calculation encourages greater network stability by not factoring in “coin age”. Therefore saving up coin age is no longer possible so nodes will need to be online more in order to get their stake reward. It'll involve a move from scrypt to SHA256 which will mean staking requires less processing power (especially helpful for mobile users wishing to stake their coins). The new system is also designed to solve security issues which made PoS v1 coins open to certain theoretical attacks. For more information see Blackcoin's Proof-of-Stake Protocol v2 white paper.
The upgrade took a great deal of work from the developers (you can view full details of the 230 changed files with 12,219 additions and 8,455 deletions here. There’s a summary of the changes in the release notes.
To participate in our public testing phase join the shadowtesting channel on slack.
ShadowGo Progress Update
We’re currently putting the finishing touches to an upgraded version of our Android wallet. This will give mobile users the full anonymizing functionality of ShadowSend v2. The beta version will be posted in the next few days for a short round of community testing before the full release. Stay tuned for further details.
ShadowMarket Progress Update
Good progress is being made on the Shadow Marketplace. Our developers expect to pick up speed now that all the necessary updates have been made to ShadowCore and a date has been scheduled for the PoS v2 hard fork. We will be working on upgrading ShadowChat for secure messaging, which will be the backbone of the whole market place, using BIP32 addresses for category trees. After that we will be working on anonymous mutltisig transactions. We are aiming to have a beta version ready for public testing and feedback within Q2. ShadowMarket will be the primary focus of our developers and the next feature to be added to the ShadowCore client.
Thank you all for your continued support and enthusiasm,
The Shadow Team
Rynomster (lead developer)
https://github.com/SDCDev/shadowcoin/commit/2a74cf11260b059c171ffdde9d43736fc41afe3a BOOM...and thanks for the dumps you weaklings 
Code:
Release Notes
+
+
+Version 1.3.2.0
+
+Changes
+ - Implemented PoS V2
+
+
+ - Removed Thin mode staking
+ The network relies on full nodes for security.
+ Staking should be a reward for maintaining a full node.
+
+
+ - Removed hash from DiskBlockIndex
+ hash is saved in the key, no need to save it twice, 32 bytes saved per block
+ Key prefix "blockindex" changed to "bidx", 36 bytes saved per block
+
+
+ The TXDB version has been raised to 70510.
+
+ On first boot the nodes will wipe any database before 70509 and initialise
+ a reindex, which will reload the TXDB from the stored blockchain.
+
+ For Databases of verson 70509 an migration will run, significantly faster
+ than a reindex. All existing nodes should be on txdb version 70509.
+
+ Thin nodes don't store the blockchain and will need to redownload.
+
+ Note: Reindexing the chain could cause your failed stake transactions to be
+ detected as occuring during the reindex, and displayed at the top of the
+ transaction list. They can be removed by running clearwallettransactions
+ followed by reloadanondata.
+
+
+
+ - Enabled unit tests
+ Compile: make -f makefile.unix test_shadow
+ Run: ./test_shadow --log_level=10
+
+
+
+
+ - printstakemodifier, printcoinstake and printcoinage are replaced by debugpos
https://github.com/SDCDev/shadowcoin/commit/2a74cf11260b059c171ffdde9d43736fc41afe3a BOOM...and thanks for the dumps you weaklings
Lots of alts taking a beating tonight.
parachutes on guys, dump time
Hello kennyP,
I'm happy that u r here with us,
welcome and keep follow Shadow project!
Lots of alts taking a beating tonight.
parachutes on guys, dump time
In 9 Days Our Thunderclap Message Will Now Be Seen By Over 1,000,000 1,200,000 People.
Join #FightForPrivacy Today By Donating Your Social Reach On Thunderclap!
Lots of alts taking a beating tonight.
why is that?No idea, but NiceHash is paying 38% over BTC. Something is going on in SHA-256 altcoin world.
Lots of alts taking a beating tonight.
why is that?
Lots of alts taking a beating tonight.
2 million SDC were destroyed for SDT (Shadow Tokens). Many of the tokens were then in turn destroyed to mint shiny new SDC
(there are not 2 million SDT currently in circulation.)But 2 million SDT were created and 2 million SDC destroyed at some point since December 2014!
Congrats!
Lots of action on Trex
Lots of interest in Shadow
Lots of new investors
And a rapidly growing community
Now326 357 372 385 390 addys with 1k+ Shadow
http://www.shadowchain.info/richlist/
Lots of interest in Shadow
Lots of new investors
And a rapidly growing community
Now
http://www.shadowchain.info/richlist/
We are going to have Shadow even if we have to fight for it.
Dead coin
The Shadow of old coin, the graph shows that this is her last times, there are now more young best coins. You have been warned.
My wallet stops syncing at block # 419887. I have been trying to have it sync for 2 days.
Try going to help, then debug window, then type command "rewindchain 1000" and press enter, and it will rewind the chain back 1000 blocks, hopefully past the troubled block, and fix the issue. This worked for me in the past on a similar issue. I think it happens if you get on a forked chain on your client. Also you can try deleting peers.dat as you may be connecting to a bad node.
this worked, thanks.
the rewind blockchain, this is a great feature
just tried thin mode, sync speed is nowhere close to electrum or multibit but it's definitely faster than normal mode. Less than 2 hours to sync the whole chain. Neat
True but Electrum and Multibit cant do what our client does... [cough cough] ZERO KNOWLEDGE and Encrypted chat built right in with much more
just tried thin mode, sync speed is nowhere close to electrum or multibit but it's definitely faster than normal mode. Less than 2 hours to sync the whole chain. Neat
My wallet stops syncing at block # 419887. I have been trying to have it sync for 2 days.
Try going to help, then debug window, then type command "rewindchain 1000" and press enter, and it will rewind the chain back 1000 blocks, hopefully past the troubled block, and fix the issue. This worked for me in the past on a similar issue. I think it happens if you get on a forked chain on your client. Also you can try deleting peers.dat as you may be connecting to a bad node.
Anyone that dumps right now will get burned. Don't take the bait, you've been warned.
Jump to: