Topic: [ANN][SILKCOIN][DARKSILK PREANN][TESTING STORMNODES/DarkSIlk MARKET/I2P] - page 25. (Read 289506 times)

active connections going up

Try 1.1.1.1

I usually point people to 1.1.0.21 if they are having issue with syncing.

Thanks.  I tried that wallet and it wouldn't run on my machine.  Is the wallet on the 1st post valid too?  1.1.1.1 Final Beta Ok to run?
Thanks...

To store your Silkcoin locally prior to the swap use - https://github.com/silkcointemple/silkcoin/releases/tag/v1.1.0.21

A guide on the swap process will be drawn up. But it is as simple as this. Send Silkcoin to Weaver wallet and then use the swap function within Weaver, done.

Ok...so right now I want to move my Silk from Polo to a local wallet.  I'm not sure on how to go about swap Silk for Darksilk but I'm assuming that I should have Silk on my own personal wallet.  Im sure you have a FAQ on how to convert Silk to Darksilk...so I'd like to read up on that asap before you guys launch. So for now...what local wallet on a windows PC do you recommend using?  Thanks.

New Silkcoin folder updated for quick sync
copy it to your user\appdata\Silkcoin folder
if you get no coins in your wallet do as Crypt0Keeper did: start the wallet with the -rescan switch

Files here On Google Drive

Good syncing

When you say what do I recommend for a wallet? Do you mean what hardware to run it on, what type of wallet i.e. headless, core, mobile etc. or do you mean Silk or DarkSilk? Little unsure on the question.

Swap will be available from the second Silk launches.

Thanks dude! Have a good one

Hi SL,

What are you recommending for a wallet?  and when is the swap feature going to be available?  Thanks...Looking forward to this.  R

1) Are there any possible attack vectors in DarkSilk that have not been patched?

one point generaly about pow/pos hybrids, pos gives you extra security to so called 30-50 attacks.
currently btc is constantly under a attack. some pools use custom software where they ignore last block submited by network(for sometime). if they can generate two blocks in a row their chain will be longest and valid. then this earlier found&ignored block ends upto be an orphan.

that can be totally be eliminated with pos/pow ratio, depens what rules dev wants to be the final ones.
i think the point is that there would never be a need to do a hardfork.

1) Are there any possible attack vectors in DarkSilk that have not been patched?

This is not really answerable until we get the last few bits of code in and begin another round of testing. However we are aware of security issues within the wallet such as the PoS hashes being tied to the Stormnodes and these for instance will be changed to the Argon2d PoW hashes. But with a 3 tier network using PoW, PoS and Stormnode Quorums I do not believe a Sybil attack would be possible.

2) What is the retarget algorithm you are using?

The retarget algorithm for difficulty is taken from Blackcoin and we have adapted the code to make it easier to read by inserting static constants. PoW and PoS have individual difficulty and it is retargeted each block.

3) What happens to header-first downloads from BitCoin Core 0.10?

We are implementing header first once we use CBlockHeader and GetBlockHeader which need to be implemented first.

4) Can staking have high CPU usage?

We are using the faster Blake2B algortihm for PoS. The CPU usage for this will come out in testing and we will update the community once we know.

5) Will running, acquiring and using the DarkSilk client tax my resources? (2 GB RAM, 3 GHz Processor)

Currently on my i5 4690k it utilises between 0%-9% and around 40MB of RAM. After we refine the GUI and CPU usage in general this will be reduced further. Short answer, no.

6) What is your take on the block debate?

I believe that because it is such an issue for Bitcoin they had to act quickly, whether they chose the correct action, I don't think so. I believe an adaptable or smartblock method should be used. BTW 'SmartBlocks' as of this moment is my own coined expression and terminology (take note lol) and if its used for something else, ill have to come up with a better name

7) How will you take care of Selfish Stake Nodes?

DarkSilk and Silk both use PoSv3 from Blackcoin i.e. Static PoS Rewards and with Split Stake. Coin age is completely removed from the equation rendering selfish stake node a problem of the past.

8 ) Now, the last question - How will you prevent monopoly?

If you mean in terms of stopping or preventing any one party investing a large amount into either DarkSilk and Silk, no, there is nothing we can do.

Also, how are you doing?

Waiting for my food still to turn up, so I answered your questions now, instead of in the morning

Mr. Lievens, sorry to interrupt - may I ask a question? (Ok! Fine, more than one)

1) Are there any possible attack vectors in DarkSilk that have not been patched?
2) What is the retarget algorithm you are using?
3) What happens to header-first downloads from BitCoin Core 0.10?
4) Can staking have high CPU usage?
5) Will running, acquiring and using the DarkSilk client tax my resources? (2 GB RAM, 3 GHz Processor)
6) What is your take on the block debate?
7) How will you take care of Selfish Stake Nodes?
8 ) Now, the last question - How will you prevent monopoly?

Also, how are you doing?

that is a one way, a short cut for many users.

just opened my btc wallet, wow i have somehow empty chain, lets wait a week..
using the:Latest "stable" version of Bitcoin Core: 0.11.2

Because of Stormnodes and their incentivisation, we will be developing headless wallets after the DarkSilk Core is released.

However a preloaded DAT file could be an option which once pulled from is deleted.

not to make too long, clear start.

about block download.
would it be too easy to have effective p2p like torrentz, make a fast buffer file for chain, and then same time load it.
current hd first just did not make btc dl any better.
every time i use my btc wallet, wait a day or two for synch, that sucks.

Too many cooks in the kitchen? I feel I took the correct route working alone and quietly from April last year until September/October time and then bringing in a team and going public fully in November/December. A year of hard work, pulling between 12 and 18 hour days, every day, including holidays. I think if you go back through GitHub there will be a commit pretty much daily going all the way back. Blocksize is quite a funny one at the moment, especially as everyone seem to be sheep and just slapping their blocksizes up to 2MB, just like Bitcoin. Well, we are thinking a bit deeper on this one and are going to take the best option that we can choose from with the current options available to us.

that never ends, it is a infinity loop to make a good one.
imagine all the work, time and number of peoples behind current btc code, and now btc is making suicide because minor things, worst one is too late and missing consensus to blocksize.

Overprinting to debug and CPU usage are on the list.

Those are in fact the last two jobs before and during the UI which is the last job.

EDIT: Last job, lol

you know how lazy i am according that.


just a feeling, darksilkgui has some part eating cpu..

Can always pull request fixes for building on your platform

Yes the Argon2d branch will be updated and merged to master.