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

[mbishop75]

Since this is not live (i.e. no hashGenesisBlock defined), the wallet crashes on assert(hashGenesisBlock == uint256("")); when trying to launch.  Do you have a block chain that you're using for dev purposes?  I'd like to connect to the same BC that you're using so we can see the same transactions et al.

[1714773175]

1714773175

[1714773175]

1714773175

[SCDeveloper]

Since this is not live (i.e. no hashGenesisBlock defined), the wallet crashes on assert(hashGenesisBlock == uint256("")); when trying to launch.  Do you have a block chain that you're using for dev purposes?  I'd like to connect to the same BC that you're using so we can see the same transactions et al.

It shouldn't crash on assert(hashGenesisBlock ==uint256("")); as it is present:

https://github.com/SCDeveloper/DarkSilk/blob/master/src/chainparams.cpp#L95

I have just cloned and built from the same repo.

https://github.com/SCDeveloper/DarkSilk

[SCDeveloper]

Since this is not live (i.e. no hashGenesisBlock defined), the wallet crashes on assert(hashGenesisBlock == uint256("")); when trying to launch.  Do you have a block chain that you're using for dev purposes?  I'd like to connect to the same BC that you're using so we can see the same transactions et al.

It shouldn't crash on assert(hashGenesisBlock ==uint256("")); as it is present:

https://github.com/SCDeveloper/DarkSilk/blob/master/src/chainparams.cpp#L95

I have just cloned and built from the same repo.

https://github.com/SCDeveloper/DarkSilk

If you find the issue could you pull request and I will merge. Believe there is a 5/6 hour difference between us and it's getting late here now.

[mbishop75]

Did you build from a fresh clone?  I had to add "qrencode.h" to ./src/qt/ to build successfully. 
Maybe you have a local reference that the repo is missing. 

If I find the issue, I'll fork your repo and do a pull request.

[mbishop75]

Oh yea...without commenting out the debug assertions for the hashGenesisBlock, the wallet does not launch on my fresh build.

DarkSilk: ../DarkSilk/src/chainparams.cpp:86: CMainParams::CMainParams(): Assertion `hashGenesisBlock == uint256("")' failed.
Aborted

I'm running 3.13.0-24-generic #47-Ubuntu (Linux Mint 17) and building with Qt 5.3.1 (GCC 4.6.1, 64 bit).
I'll check for updates and re-build to see if that makes a difference.  It's not a show stopper by any means. 

[SCDeveloper]

Oh yea...without commenting out the debug assertions for the hashGenesisBlock, the wallet does not launch on my fresh build.

DarkSilk: ../DarkSilk/src/chainparams.cpp:86: CMainParams::CMainParams(): Assertion `hashGenesisBlock == uint256("")' failed.
Aborted

I'm running 3.13.0-24-generic #47-Ubuntu (Linux Mint 17) and building with Qt 5.3.1 (GCC 4.6.1, 64 bit).
I'll check for updates and re-build to see if that makes a difference.  It's not a show stopper by any means.  

That is strange.

I created a clean Ubuntu (15.04) VM and cloned the repo. Followed my ReadMe to the letter (to make sure I hadn't missed anything) and it built and ran perfectly first time. Both daemon and Qt.

Check you have these deps: libpng-dev qrencode libqrencode-dev

You should not have to add qrencode.h to the source.

[OrsonJ]

Oh yea...without commenting out the debug assertions for the hashGenesisBlock, the wallet does not launch on my fresh build.

DarkSilk: ../DarkSilk/src/chainparams.cpp:86: CMainParams::CMainParams(): Assertion `hashGenesisBlock == uint256("")' failed.
Aborted

I'm running 3.13.0-24-generic #47-Ubuntu (Linux Mint 17) and building with Qt 5.3.1 (GCC 4.6.1, 64 bit).
I'll check for updates and re-build to see if that makes a difference.  It's not a show stopper by any means.  

That is strange.

I created a clean Ubuntu (15.04) VM and cloned the repo. Followed my ReadMe to the letter (to make sure I hadn't missed anything) and it built and ran perfectly first time. Both daemon and Qt.

Check you have these deps: libpng-dev qrencode libqrencode-dev

You should not have to add qrencode.h to the source.

I have it built and running on 14.04. Slow syncing, seems to be stuck on 3 blocks but I'll leave it a bit. Digging those keyboard shortcuts!  

[SCDeveloper]

Oh yea...without commenting out the debug assertions for the hashGenesisBlock, the wallet does not launch on my fresh build.

DarkSilk: ../DarkSilk/src/chainparams.cpp:86: CMainParams::CMainParams(): Assertion `hashGenesisBlock == uint256("")' failed.
Aborted

I'm running 3.13.0-24-generic #47-Ubuntu (Linux Mint 17) and building with Qt 5.3.1 (GCC 4.6.1, 64 bit).
I'll check for updates and re-build to see if that makes a difference.  It's not a show stopper by any means.  

That is strange.

I created a clean Ubuntu (15.04) VM and cloned the repo. Followed my ReadMe to the letter (to make sure I hadn't missed anything) and it built and ran perfectly first time. Both daemon and Qt.

Check you have these deps: libpng-dev qrencode libqrencode-dev

You should not have to add qrencode.h to the source.

I have it built and running on 14.04. Slow syncing, seems to be stuck on 3 blocks but I'll leave it a bit. Digging those keyboard shortcuts!  

Not stuck. That's how many blocks the chain consists of

[OrsonJ]

Oh yea...without commenting out the debug assertions for the hashGenesisBlock, the wallet does not launch on my fresh build.

DarkSilk: ../DarkSilk/src/chainparams.cpp:86: CMainParams::CMainParams(): Assertion `hashGenesisBlock == uint256("")' failed.
Aborted

I'm running 3.13.0-24-generic #47-Ubuntu (Linux Mint 17) and building with Qt 5.3.1 (GCC 4.6.1, 64 bit).
I'll check for updates and re-build to see if that makes a difference.  It's not a show stopper by any means.  

That is strange.

I created a clean Ubuntu (15.04) VM and cloned the repo. Followed my ReadMe to the letter (to make sure I hadn't missed anything) and it built and ran perfectly first time. Both daemon and Qt.

Check you have these deps: libpng-dev qrencode libqrencode-dev

You should not have to add qrencode.h to the source.

I have it built and running on 14.04. Slow syncing, seems to be stuck on 3 blocks but I'll leave it a bit. Digging those keyboard shortcuts!  

Not stuck. That's how many blocks the chain consists of

My mistake, it's saying 'Out of Sync' but presumably because it's been a few hours since that last block was mined. One thing I noticed - if I try to create a Stormnode address the wallet closes abruptly after entering it. Don't know if that's the standard behaviour with Crave or if it's crashing. The address is listed when restarting the wallet. Let me know if there's anything I can do to help with testing.

[SCDeveloper]

Oh yea...without commenting out the debug assertions for the hashGenesisBlock, the wallet does not launch on my fresh build.

DarkSilk: ../DarkSilk/src/chainparams.cpp:86: CMainParams::CMainParams(): Assertion `hashGenesisBlock == uint256("")' failed.
Aborted

I'm running 3.13.0-24-generic #47-Ubuntu (Linux Mint 17) and building with Qt 5.3.1 (GCC 4.6.1, 64 bit).
I'll check for updates and re-build to see if that makes a difference.  It's not a show stopper by any means.  

That is strange.

I created a clean Ubuntu (15.04) VM and cloned the repo. Followed my ReadMe to the letter (to make sure I hadn't missed anything) and it built and ran perfectly first time. Both daemon and Qt.

Check you have these deps: libpng-dev qrencode libqrencode-dev

You should not have to add qrencode.h to the source.

I have it built and running on 14.04. Slow syncing, seems to be stuck on 3 blocks but I'll leave it a bit. Digging those keyboard shortcuts!  

Not stuck. That's how many blocks the chain consists of

My mistake, it's saying 'Out of Sync' but presumably because it's been a few hours since that last block was mined. One thing I noticed - if I try to create a Stormnode address the wallet closes abruptly after entering it. Don't know if that's the standard behaviour with Crave or if it's crashing. The address is listed when restarting the wallet. Let me know if there's anything I can do to help with testing.

The wallet doesn't crash however when you run it using:

$ valgrind --tool=memcheck --leak-check=full ./DarkSilk

which was what I was doing to see if I could find the root of the invalid pointer issue.

You will have to sudo apt-get install valgrind so that you can see this.

Also if your mining to the wallet, even if you close the wallet, it will stay running in the background until you quit the miner.

Also I haven't experienced the crash from creating a Stormnode.

[SCDeveloper]

OK I believe I have fixed it (no more errors).

The wallet no longer crashes on mining.

Can everyone clone and rebuild please

Also clear out all files except your darksilk.conf within your hidden .darksilk folder in ~

https://github.com/SCDeveloper/DarkSilk/commit/98f02e43cdd9d3738a3634088aa025dd2ddf6e7a

EDIT: Now 7.10am and been up fixing the error and sorting the mining out. Cleaned out unused code and also implemeneted two bitcoin commits.

https://i.imgur.com/GdGEVZB.png


Was also thinking......how about 4.2% PoS Interest?

[OrsonJ]

OK I believe I have fixed it (no more errors).

The wallet no longer crashes on mining.

Can everyone clone and rebuild please

Also clear out all files except your darksilk.conf within your hidden .darksilk folder in ~

https://github.com/SCDeveloper/DarkSilk/commit/98f02e43cdd9d3738a3634088aa025dd2ddf6e7a

EDIT: Now 7.10am and been up fixing the error and sorting the mining out. Cleaned out unused code and also implemeneted two bitcoin commits.




Was also thinking......how about 4.2% PoS Interest?

Lol and rpcport 4242? 

[SCDeveloper]

OK I believe I have fixed it (no more errors).

The wallet no longer crashes on mining.

Can everyone clone and rebuild please

Also clear out all files except your darksilk.conf within your hidden .darksilk folder in ~

https://github.com/SCDeveloper/DarkSilk/commit/98f02e43cdd9d3738a3634088aa025dd2ddf6e7a

EDIT: Now 7.10am and been up fixing the error and sorting the mining out. Cleaned out unused code and also implemeneted two bitcoin commits.

https://i.imgur.com/GdGEVZB.png


Was also thinking......how about 4.2% PoS Interest?

Lol and rpcport 4242? 

We will see lol

[HORT]

I do hope the new wallet is not as big of memory hog as the last wallet. The current wallet (1.1.1.1) uses a minimum 15% CPU and spikes to 30%. Is this addressable? Thanks!!

[SCDeveloper]

I do hope the new wallet is not as big of memory hog as the last wallet. The current wallet (1.1.1.1) uses a minimum 15% CPU and spikes to 30%. Is this addressable? Thanks!!

Well the original Silkcoin wallet does have a lot of features within it, hence the CPU and RAM usage.

[SCDeveloper]

Connect to the #DarkSilkTestNet channel on the Freenode IRC network to communicate together.

We may need to clear out the chain at points and obviously we cannot always get messages across to people quickly enough via here.

If anyone has downloaded the source from GitHub then please download again as changes have been made.

Ensure you clear out all your data apart from darksilk.conf from the .darksilk (hidden) directory.

(There is a darksilk.conf included in the DarkSilk/src directory)

[SCDeveloper]

How many people can provide seeds upon launch?

Clearnet (IPv4 and IPv6), Tor and I2P.

This way I can add the addresses to the darksilk.conf provided and also into the source:

https://github.com/SCDeveloper/DarkSilk/tree/master/share/seeds

[HORT]

OK all, we need to start on a logo design for DarkSilk. Let the submissions begin!!

[SCDeveloper]

https://i.imgur.com/pY3IiJ5.png

Another variation on the same design.

(I am no pro graphic designer by a long shot lol)

[Delita Heiral]

nintendo darksilk