[ANN][SILKCOIN][DARKSILK PREANN][TESTING STORMNODES/DarkSIlk MARKET/I2P]

[yell4george]

Hello DarkSilk and SilkNetwork members.  I just wanted to let you all know that in a few days here I will have some screenshots of the SilkNetwork website.  I'll be looking for some input on the layout and styling of the site to see what everyone's opinion is.  Feel free to contact me @ m.langdon@silknetwork.org if you have any ideas or suggestions.  Hope you all had a very good Christmas and enjoy your New Year!

How's the website coming? We're all primed and ready to spread the word about Silk Network ..

[1715154882]

1715154882

[1715154882]

1715154882

[1715154882]

1715154882

[1715154882]

1715154882

[glavos]

I remember that i lost loot of money with silk on mintpal, i wish that this project goes much better this time.  

[SLievensDRKSLK]

More than the splash screen should do the code, am I right? The glittering is important but if this coin wants to have a good start everything must be good and good-looking fresh from the start.
Waiting for news from you 

It is all important

[pescadorloco69]

Hi Guys n Gals

I am getting an assertion failed error on starting the wallet.

It was staking and running fine but now  getting this.

Win7 64bit
Wallet ver 1.1.1.1

If anyone can help it would be appreciated.

P.S Lovin the new logos

Use this version - https://github.com/silkcointemple/silkcoin/releases/tag/v1.1.0.21

Clear your chain and use the bootstrap from here - https://github.com/scdeveloper

Good luck

Thanks for the reply Spencer.

I tried this last night but hangs on loading the bootstrap..any ideas?

Silk has worked fine until now.

Thanks

[SLievensDRKSLK]

We are still testing and working on code.

Here is how the wallet looks as of now:



The UI will have a lot of work done to it before we release publicly i.e. Layout/Colours.

EDIT: Here is what we are working on when is comes to the DarkSilk wallet:

Code:

1) To finish stormnode update stormnodemanager (UI), sandstorm UI andcheck main.cpp/h, wallet.cpp/h and others for SN usage.

2) Transaction sending errors fix.

3) ERROR: AcceptToMemoryPool : coinstake as individual tx see https://github.com/dashpay/dash/commit/97c97f7e40cf1e00681d336a4bfc2f7d54ed7af6

4) Implement Argon2d/blake2b.

5) Implement CChain, ChainActive.

6) Implement getblockheaders, Headers-first synchronization.

7) Make sure we are using the PoW hashes for DarkSilk's stormnode rewards. Params().LastPOWBlock() 
   SN payment selection needs to be coupled to PoW blocks, not PoS and make sure we never use a PoS hash for stormnode scores. 

8) Collateral addresses.

9) interpreter.h

10) EXCEPTION: St12out_of_range       
basic_string::replace: __pos (which is 18446744073709551615) > this->size() (which is 0)       
darksilk in ProcessMessages()  --Not sure if this is an issue.

11) Check to see if this has been implemented: DER signatures... see https://github.com/bitcoin/bitcoin/pull/5713/files src/scripts/. . https://github.com/bitcoin/bips/blob/master/bip-0066.mediawiki
https://bitcointalk.org/index.php?topic=8392.msg127623#msg127623  Check for canonical public keys and signatures

12) Writing unit tests.

13) Blocksize - ?combination of previous tx's in block being looked at? and a hardcoded blocksize increase according to ntime?.

14) ??? select coins:  https://github.com/EvgenijM86/emercoin/commit/14374e710ae0039b4af3878eac8ce44e27563d95

15) CPU use for UI is high.

16) Reduce over printing to debug.log

[nzminer]

Judgecrypto, are you still around? 

[NoobKidOnTheBlock]

So am I safe to guess that once you guys got everything going good for DRKSILK then you will be doing the swap? I just want to make sure that I don't miss it that's all

[SLievensDRKSLK]

So am I safe to guess that once you guys got everything going good for DRKSILK then you will be doing the swap? I just want to make sure that I don't miss it that's all

Yes once everything is ready we will start going ahead.

[NoobKidOnTheBlock]

So am I safe to guess that once you guys got everything going good for DRKSILK then you will be doing the swap? I just want to make sure that I don't miss it that's all

Yes once everything is ready we will start going ahead.

Cool I will be paying close attention

[Karartma1]

Wallet GUI looks ok but work on those colors: it does not seem eye-friendly to me. In any case it seems like there's a bit of work to be done prior to release. It's good you did not give any dates here. Creating suspense is the best thing to do in crypto!

[TheLastTrapper]

Hey I'm new to trading but my buddy turned me onto this project and he mentioned something about a swap supposed to occur sometime and I wanted to know what will have to be done when that happens? I'm really new to this whole experience and don't really know what I'm exactly doing so any help would be greatly appreciated.

[Empinel]

We are still testing and working on code.

Here is how the wallet looks as of now:



The UI will have a lot of work done to it before we release publicly i.e. Layout/Colours.

EDIT: Here is what we are working on when is comes to the DarkSilk wallet:

Code:

1) To finish stormnode update stormnodemanager (UI), sandstorm UI andcheck main.cpp/h, wallet.cpp/h and others for SN usage.

2) Transaction sending errors fix.

3) ERROR: AcceptToMemoryPool : coinstake as individual tx see https://github.com/dashpay/dash/commit/97c97f7e40cf1e00681d336a4bfc2f7d54ed7af6

4) Implement Argon2d/blake2b.

5) Implement CChain, ChainActive.

6) Implement getblockheaders, Headers-first synchronization.

7) Make sure we are using the PoW hashes for DarkSilk's stormnode rewards. Params().LastPOWBlock() 
   SN payment selection needs to be coupled to PoW blocks, not PoS and make sure we never use a PoS hash for stormnode scores. 

8) Collateral addresses.

9) interpreter.h

10) EXCEPTION: St12out_of_range       
basic_string::replace: __pos (which is 18446744073709551615) > this->size() (which is 0)       
darksilk in ProcessMessages()  --Not sure if this is an issue.

11) Check to see if this has been implemented: DER signatures... see https://github.com/bitcoin/bitcoin/pull/5713/files src/scripts/. . https://github.com/bitcoin/bips/blob/master/bip-0066.mediawiki
https://bitcointalk.org/index.php?topic=8392.msg127623#msg127623  Check for canonical public keys and signatures

12) Writing unit tests.

13) Blocksize - ?combination of previous tx's in block being looked at? and a hardcoded blocksize increase according to ntime?.

14) ??? select coins:  https://github.com/EvgenijM86/emercoin/commit/14374e710ae0039b4af3878eac8ce44e27563d95

15) CPU use for UI is high.

16) Reduce over printing to debug.log

Well good job! Think you should join SuperNET or BlockNET as well

[SLievensDRKSLK]

Wallet GUI looks ok but work on those colors: it does not seem eye-friendly to me. In any case it seems like there's a bit of work to be done prior to release. It's good you did not give any dates here. Creating suspense is the best thing to do in crypto!

Like I said in my previous post, styling and colours are not final and still need to do a load of work on the UI.

EDIT: The UI is the last thing to do once everything else is complete.

[SLievensDRKSLK]

We have created a page and group for all you Facebook users out there. come and give us a like and get involved in the group

Facebook Page - https://www.facebook.com/Silk-Network-620931718072997/
Facebook Group - https://www.facebook.com/groups/silknetwork/

[SLievensDRKSLK]

Made good progress and now we just have these jobs left to do:

Code:

1) Implement CChain, ChainActive.

2) Implement getblockheaders, Headers-first synchronization.

3) interpreter.h

4) Implement Argon2d/blake2b.

5) Make sure we are using the PoW hashes for DarkSilk's stormnode rewards. Params().LastPOWBlock() 
   SN payment selection needs to be coupled to PoW blocks, not PoS and make sure we never use a PoS hash for stormnode scores. 

6) Collateral addresses.

7) To finish stormnode update stormnodemanager (UI), sandstorm UI andcheck main.cpp/h, wallet.cpp/h and others for SN usage.

8) Blocksize.

9) ERROR: AcceptToMemoryPool : coinstake as individual tx see https://github.com/dashpay/dash/commit/97c97f7e40cf1e00681d336a4bfc2f7d54ed7af6

10) SelectCoins:  https://github.com/EvgenijM86/emercoin/commit/14374e710ae0039b4af3878eac8ce44e27563d95

11) EXCEPTION: St12out_of_range       
basic_string::replace: __pos (which is 18446744073709551615) > this->size() (which is 0)       
darksilk in ProcessMessages()  --Not sure if this is an issue.

12) Writing unit tests.

13) Finalise Styling

[SLievensDRKSLK]

Silk is ready in terms of styling and splashscreen, code is also all done except for watch only addresses within the GUI. The watch only address feature is something that no one has within their GUI and has been worked on by Alistair (Infernoman) and credit must go to him and his hard work.

DarkSilk just needs a few fixes carried out and the marketplace adding to the codebase, along with the other items in the list posted above. The team is really happy with the work carried out and being carried out.

Weaver is still under development...this is something of course that will never truly end, with your input and suggestions we hope to create an enterprise platform for users of the Silk Network that wil grow and adapt for years to come. Currently security for users is our key concern with optional user pins and 2FA implemented recently. The web address for Weaver will be https://weaver.silknetwork.org and the first time people will see the platform will be when we open for user registrations in preparation for the Silkcoin to Silk swap.

Now we all know you all want timeframes. Here is the plan. Get DarkSilk finished and Weaver functional. Silk is effectively ready. DarkSilk should take a maximum of 4-6 weeks to be finalised. This means we are aiming for a March launch for Silk if not before, if everything goes smoothly without finding more errors along the way. DarkSilk then would be launched in April. The Crowdsale would then happen with full Weaver functionality aimed for April/May. At this point we would then be working on new features set out by ourselves and suggestions put forward by the community.

In the long term we will be looking to have Silk and DarkSilk work off of each other, in both a blockchain and real world sense. Price stability and distribution being the key focal point. This is something that has been planned, worked upon and will be set into action. This is a currency we want all Bitcoin users to be questioning to switch to, altcoin users to use without question and new adopters to choose over all others.

[yell4george]

Silk is ready in terms of styling and splashscreen, code is also all done except for watch only addresses within the GUI. The watch only address feature is something that no one has within their GUI and has been worked on by Alistair (Infernoman) and credit must go to him and his hard work.

DarkSilk just needs a few fixes carried out and the marketplace adding to the codebase, along with the other items in the list posted above. The team is really happy with the work carried out and being carried out.

Weaver is still under development...this is something of course that will never truly end, with your input and suggestions we hope to create an enterprise platform for users of the Silk Network that wil grow and adapt for years to come. Currently security for users is our key concern with optional user pins and 2FA implemented recently. The web address for Weaver will be https://weaver.silknetwork.org and the first time people will see the platform will be when we open for user registrations in preparation for the Silkcoin to Silk swap.

Now we all know you all want timeframes. Here is the plan. Get DarkSilk finished and Weaver functional. Silk is effectively ready. DarkSilk should take a maximum of 4-6 weeks to be finalised. This means we are aiming for a March launch for Silk if not before, if everything goes smoothly without finding more errors along the way. DarkSilk then would be launched in April. The Crowdsale would then happen with full Weaver functionality aimed for April/May. At this point we would then be working on new features set out by ourselves and suggestions put forward by the community.

In the long term we will be looking to have Silk and DarkSilk work off of each other, in both a blockchain and real world sense. Price stability and distribution being the key focal point. This is something that has been planned, worked upon and will be set into action. This is a currency we want all Bitcoin users to be questioning to switch to, altcoin users to use without question and new adopters to choose over all others.

Great news Thanks for sharing! Much anticipation for this project with so much potential. The last paragraph ^^ makes me smile. A binary coin feedback system

[NoobKidOnTheBlock]

Man I can't wait for this DRKSLK to be released This is going to be a good coin to be holding that's for sure by the sounds of it

[SLievensDRKSLK]

Hey I'm new to trading but my buddy turned me onto this project and he mentioned something about a swap supposed to occur sometime and I wanted to know what will have to be done when that happens? I'm really new to this whole experience and don't really know what I'm exactly doing so any help would be greatly appreciated.

Best to have a good read of the thread from around page 116 onwards - https://bitcointalk.org/index.php?topic=676976.2300.

My username at that point was SCDeveloper, hence the current GitHub username

[pescadorloco69]

I finally got my silk wallet back up and running and staking away.

Thanks for the advice Spencer