[*] 8BIT [Dark Masternodes][Anon][Roadmap Stage 4]

[8-bit-Party]

It's an option too, but the problem is what if the current problems are in the blockchain and can't be fixed, we tried for 2 months already.  with coin swap to clean chain, we know we get fast syncing coin, plus the new Dash features.

Really?
We need powerusers (e.g. allZuckedUp) to check new branch

NOTE: following test has been performed on VIRTUALIZED enviroment. Host setup:
- CPU: pretty OLD i5, MOBILE version
- SATA HDD
- 1.5G RAM
so  - nothing fancy

let's compile and start daemon

Code:

git clone -b fixed_sync https://github.com/8bit-dev/8bit.git && cd 8bit/src/ && make -f makefile.unix -j2 && strip -s 8bitd && mv 8bitd ~ && cd
wget http://www.8-bit.party/static/bootstrap.dat.bz2 && bunzip2 bootstrap.dat.bz2 && mkdir .8bit && mv boostrap.dat .8bit
vi .8bit/8bit.conf (... par=2 dbcache=120)
./8bitd

let's go

Code:

Mon 31 Aug 20:23:43 BST 2015
8Bit server starting

we start with empty databases

Code:

init message: Loading addresses...
ERROR: CAddrman::Read() : open failed
Invalid or missing peers.dat; recreating
Loaded 0 addresses from peers.dat  0ms

new feature

Code:

[bootstrap.dat] Loading blockfile from external file /home/party8bit/.8bit/bootstrap.dat

let's get current height / other (fully synced) node

Code:

date;./8bitd -datadir=.8bit getblockcount
Mon Aug 31 22:25:17 CEST 2015
173326

let's see where are we now

Code:

date;tail -2 .8bit/debug.log
Mon 31 Aug 21:25:19 BST 2015
SetBestChain: new best=c7529a4b12f3b11793066ed4db027125a3eb1744005d661236f1b2f5ee81e6c8  height=30239  trust=211906661110443464  blocktrust=5222802184991  date=05/11/15 16:08:16
ProcessBlock: ACCEPTED

So with updated code and fresh bootstrap.dat, after one hour I have synced my chain up to height 30239 what basically means that it took me about one hour to download 17.4% of blockchain. So within 6 hours I will have fully synced, almost 5 months old 8BIT blockchain.

[1714724546]

1714724546

[dbt1033]

It's an option too, but the problem is what if the current problems are in the blockchain and can't be fixed, we tried for 2 months already.  with coin swap to clean chain, we know we get fast syncing coin, plus the new Dash features.

Really?
We need powerusers (e.g. allZuckedUp) to check new branch

NOTE: following test has been performed on VIRTUALIZED enviroment. Host setup:
- CPU: pretty OLD i5, MOBILE version
- SATA HDD
- 1.5G RAM
so  - nothing fancy

let's compile and start daemon

Code:

git clone -b fixed_sync https://github.com/8bit-dev/8bit.git && cd 8bit/src/ && make -f makefile.unix -j2 && strip -s 8bitd && mv 8bitd ~ && cd
wget http://www.8-bit.party/static/bootstrap.dat.bz2 && bunzip2 bootstrap.dat.bz2 && mkdir .8bit && mv boostrap.dat .8bit
vi .8bit/8bit.conf (... par=2 dbcache=120)
./8bitd

let's go

Code:

Mon 31 Aug 20:23:43 BST 2015
8Bit server starting

we start with empty databases

Code:

init message: Loading addresses...
ERROR: CAddrman::Read() : open failed
Invalid or missing peers.dat; recreating
Loaded 0 addresses from peers.dat  0ms

new feature

Code:

[bootstrap.dat] Loading blockfile from external file /home/party8bit/.8bit/bootstrap.dat

let's get current height / other (fully synced) node

Code:

date;./8bitd -datadir=.8bit getblockcount
Mon Aug 31 22:25:17 CEST 2015
173326

let's see where are we now

Code:

date;tail -2 .8bit/debug.log
Mon 31 Aug 21:25:19 BST 2015
SetBestChain: new best=c7529a4b12f3b11793066ed4db027125a3eb1744005d661236f1b2f5ee81e6c8  height=30239  trust=211906661110443464  blocktrust=5222802184991  date=05/11/15 16:08:16
ProcessBlock: ACCEPTED

So with updated code and fresh bootstrap.dat, after one hour I have synced my chain up to height 30239 what basically means that it took me about one hour to download 17.4% of blockchain. So within 6 hours I will have fully synced, almost 5 months old 8BIT blockchain.

That's actually not too bad...

I would really like to see lite mode features implemented into the wallet at some point (like shadowcash, not sure what other coins have it).

I've never had syncing issues myself.

[Tinkles]

So with updated code and fresh bootstrap.dat, after one hour I have synced my chain up to height 30239 what basically means that it took me about one hour to download 17.4% of blockchain. So within 6 hours I will have fully synced, almost 5 months old 8BIT blockchain.

I see that's your repo not the original one, so does the above have any of the checkpoint fixes?

I wonder what is the time difference without the bootstrap also?  I am on windows so I am guessing it's not going to be easy to build.

6 hours is still quite long, Dash is around 40 minutes and the chain is a lot bigger, although it will have more bandwidth available with all the nodes Dash has.

EDIT: Just looking at Github, so some fixes for checkpoints and orphans?  https://github.com/8bit-dev/8bit/commit/56e70723e74c65c1d9eb61334be9801ee276d208 it would be good to try a windows version

EDIT2: whats the situation with dependencies, how much work is it to get this building on Ubuntu?

[allZuckedUp]

EDIT2: whats the situation with dependencies, how much work is it to get this building on Ubuntu?

I have not played with the code yet at all... That's going to have to wait for me to finish with my regular IT day job for today... BUT, from things I've posted previously... Your general steps to compile are LIKELY something like this...

Again... !!!WARNING!!!  This is totally untested, compile at your own risk, don't put real amounts of funding on this until you're sure it works... And if somehow this fucks you in some way, I told you so!

• mkdir <directory you want this to live in>
• cd <that directory>
• sudo apt-get install build-essential libssl-dev libdb++-dev libboost-all-dev libqrencode-dev libminiupnpc-dev
• git clone https://github.com/bitcoin/secp256k1.git
• cd secp256k1
• git checkout a1d5ae1
• ./autogen.sh
• ./configure
• make
• sudo make install
• sudo ldconfig
• cd ..
• git clone https://github.com/8bit-dev/8bit
• cd 8bit/src/
• mkdir obj/crypto
• make -f makefile.unix -j2
• strip -s 8bitd
• mv 8bitd <where ever you want it to live>
• mkdir ~/.8bit
• mv boostrap.dat ~/.8bit

AGAIN... I make no guarantees this works... ever. Evar!!!
But, I will absolutely be compiling this myself tonight (not even starting until after 10pm MDT), and I will update with what worked for me.

EDIT: You might not need everything from *git clone https://github.com/bitcoin/secp256k1.git* to *cd ..*, OR you might need it but not the *git checkout a1d5ae1* step, depending on where 8-bit-party got with his code.  I'll let you all know later.

[Tinkles]

EDIT2: whats the situation with dependencies, how much work is it to get this building on Ubuntu?

I have not played with the code yet at all... That's going to have to wait for me to finish with my regular IT day job for today... BUT, from things I've posted previously... Your general steps to compile are LIKELY something like this...

Again... !!!WARNING!!!  This is totally untested, compile at your own risk, don't put real amounts of funding on this until you're sure it works... And if somehow this fucks you in some way, I told you so!

• mkdir <directory you want this to live in>
• cd <that directory>
• sudo apt-get install build-essential libssl-dev libdb++-dev libboost-all-dev libqrencode-dev libminiupnpc-dev
• git clone https://github.com/bitcoin/secp256k1.git
• cd secp256k1
• git checkout a1d5ae1
• ./autogen.sh
• ./configure
• make
• sudo make install
• sudo ldconfig
• cd ..
• git clone https://github.com/8bit-dev/8bit
• cd 8bit/src/
• mkdir obj/crypto
• make -f makefile.unix -j2
• strip -s 8bitd
• mv 8bitd <where ever you want it to live>
• mkdir ~/.8bit
• mv boostrap.dat ~/.8bit

AGAIN... I make no guarantees this works... ever. Evar!!!
But, I will absolutely be compiling this myself tonight (not even starting until after 10pm MDT), and I will update with what worked for me.

EDIT: You might not need everything from *git clone https://github.com/bitcoin/secp256k1.git* to *cd ..*, OR you might need it but not the *git checkout a1d5ae1* step, depending on where 8-bit-party got with his code.  I'll let you all know later.

Awesome! Muchos gracias allZuckedUp.  I'm just downloading Ubuntu desktop...looks like it's finally time to get into some coin builds 

Let us know how your compiling goes or any tweaks to the above

[8-bit-Party]

Yes, it's a new version with checkpoints and small fix.
When cloning repo note -b fixed_sync switch

Code:

git clone -b fixed_sync https://github.com/8bit-dev/8bit.git

Unlike most of altcoins DASH sync is very fast, because it's code has been merged with fresh Bitcoin Core. Bitcoin Core offers so called headers-first feature which dramatically reduces blockchain download time. So this is actually why it's worth to base on current DASH code.
However, it does NOT mean you HAVE TO make a coin swap to base on current DASH code.

[Tinkles]

Yes, it's a new version with checkpoints and small fix.
When cloning repo note -b fixed_sync switch

Code:

git clone -b fixed_sync https://github.com/8bit-dev/8bit.git

Unlike most of altcoins DASH sync is very fast, because it's code has been merged with fresh Bitcoin Core. Bitcoin Core offers so called headers-first feature which dramatically reduces blockchain download time. So this is actually why it's worth to base on current DASH code.
However, it does NOT mean you HAVE TO make a coin swap to base on current DASH code.

I agree.  It's just an option, but quite an attractive one - ultra-fast syncing, instant transactions, blockchain governance, optional anonymity, masternodes, x11 mining...

[skidog]

Always willing to donate coins. Not sure I would donoate 4k but I am saving my POS for a dev. I dont want to give it to a dev that would just dump on the market.  Would rather send btc then.

[dbt1033]

Always willing to donate coins. Not sure I would donoate 4k but I am saving my POS for a dev. I dont want to give it to a dev that would just dump on the market.  Would rather send btc then.

I just want our savior to have a piece of the pie.  He would receive it in increments to prevent him from dumping on us, but it should provide him with incentive to increase the value of the coin.


I do like the idea of the DASH fork, but what does everyone else think about auxPOW or switching algorithms to sha or blake?

[8-bit-Party]

switching algorithms to sha or blake?

What for?
Have you found any weakness in scrypt?

[dbt1033]

switching algorithms to sha or blake?

What for?
Have you found any weakness in scrypt?

I like scrypt, even though it's memory and power intensive.

But DASH is X11.  I've heard discussions regarding the longevity and security of chained algorithms, but I am not an expert on the matter so I cannot comment.


I like SHA and Blake for two reasons mainly.  Power efficiency (watts per gh/s) as well as security.

I know that both of these algorithms have the potential to merge mine, which should help with distribution and network security.


I don't think anyone has forked DASH in such a way before, which could attract attention on its own.


Just thinking out loud though.  I'm interested to see what you and the rest of the community think.

[Tinkles]

switching algorithms to sha or blake?

What for?
Have you found any weakness in scrypt?

I like scrypt, even though it's memory and power intensive.

But DASH is X11.  I've heard discussions regarding the longevity and security of chained algorithms, but I am not an expert on the matter so I cannot comment.


I like SHA and Blake for two reasons mainly.  Power efficiency (watts per gh/s) as well as security.

I know that both of these algorithms have the potential to merge mine, which should help with distribution and network security.


I don't think anyone has forked DASH in such a way before, which could attract attention on its own.


Just thinking out loud though.  I'm interested to see what you and the rest of the community think.

It's interesting, it's more work though.  If we just fork Dash as it is, easier and cheaper to do it quickly and without complications.  And X11 is a great algo IMHO.

[allZuckedUp]

So, as of yet, I have been unable to get this to compile at all...

It continues to fail with the "recipe for obj/key.o", which obviously screams secp256k1.

So I've tried compiling the new code with secp256k1 installed at both the latest git commit, and the infamous a1d5ae1 revision, still no compile love.

I've tried this on fresh installs of both 64bit Ubuntu 14.04 server, and 32bit debian Jessie, and also an existing install of crunchbang++ (basically debian jessie), and that last box can successfully build the current released version of the 8bit wallet just fine...

Here's the useful bits if you've seen it before... (this attempt was with the older revision of secp256k1, but I've tried with the new version too.. same result)

Ideas?

Code:

g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -DUSE_SECP256K1 -I/home/eightbit/8bit/8bit/src -I/home/eightbit/8bit/8bit/src/obj -DUSE_UPNP=0 -DENABLE_WALLET -I/home/eightbit/8bit/8bit/src/leveldb/include -I/home/eightbit/8bit/8bit/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/main.d -o obj/main.o main.cpp
key.cpp: In constructor ‘{anonymous}::CSecp256k1Init::CSecp256k1Init()’:
key.cpp:30:25: error: ‘SECP256K1_START_SIGN’ was not declared in this scope
         secp256k1_start(SECP256K1_START_SIGN);
                         ^
key.cpp:30:45: error: ‘secp256k1_start’ was not declared in this scope
         secp256k1_start(SECP256K1_START_SIGN);
                                             ^
key.cpp: In destructor ‘{anonymous}::CSecp256k1Init::~CSecp256k1Init()’:
key.cpp:33:24: error: ‘secp256k1_stop’ was not declared in this scope
         secp256k1_stop();
                        ^
key.cpp: In member function ‘bool CKey::SetPrivKey(const CPrivKey&, bool)’:
key.cpp:470:90: error: cannot convert ‘unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ec_privkey_import(const secp256k1_context_t*, unsigned char*, const unsigned char*, int)’
     if (!secp256k1_ec_privkey_import((unsigned char*)begin(), &privkey[0], privkey.size()))
                                                                                          ^
key.cpp: In member function ‘CPrivKey CKey::GetPrivKey() const’:
key.cpp:489:105: error: cannot convert ‘const unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ec_privkey_export(const secp256k1_context_t*, const unsigned char*, unsigned char*, int*, int)’
     int ret = secp256k1_ec_privkey_export(begin(), (unsigned char*)&privkey[0], &privkeylen, fCompressed);
                                                                                                         ^
key.cpp: In member function ‘CPubKey CKey::GetPubKey() const’:
key.cpp:505:101: error: cannot convert ‘unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ec_pubkey_create(const secp256k1_context_t*, unsigned char*, int*, const unsigned char*, int)’
     int ret = secp256k1_ec_pubkey_create((unsigned char*)pubkey.begin(), &clen, begin(), fCompressed);
                                                                                                     ^
key.cpp: In member function ‘bool CKey::Sign(const uint256&, std::vector<unsigned char>&) const’:
key.cpp:527:134: error: cannot convert ‘const unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ecdsa_sign(const secp256k1_context_t*, const unsigned char*, unsigned char*, int*, const unsigned char*, secp256k1_nonce_function_t, const void*)’
         if (secp256k1_ecdsa_sign(hash.begin(), (unsigned char*)&vchSig[0], &nSigLen, begin(),  secp256k1_nonce_function_rfc6979, NULL))
                                                                                                                                      ^
key.cpp: In member function ‘bool CKey::SignCompact(const uint256&, std::vector<unsigned char>&) const’:
key.cpp:551:131: error: cannot convert ‘const unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ecdsa_sign_compact(const secp256k1_context_t*, const unsigned char*, unsigned char*, const unsigned char*, secp256k1_nonce_function_t, const void*, int*)’
         if (int ret = secp256k1_ecdsa_sign_compact(hash.begin(), &vchSig[1], begin(), secp256k1_nonce_function_rfc6979, NULL, &rec))
                                                                                                                                   ^
key.cpp:551:17: warning: unused variable ‘ret’ [-Wunused-variable]
         if (int ret = secp256k1_ecdsa_sign_compact(hash.begin(), &vchSig[1], begin(), secp256k1_nonce_function_rfc6979, NULL, &rec))
                 ^
key.cpp: In member function ‘bool CKey::Load(CPrivKey&, CPubKey&, bool)’:
key.cpp:567:90: error: cannot convert ‘unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ec_privkey_import(const secp256k1_context_t*, unsigned char*, const unsigned char*, int)’
     if (!secp256k1_ec_privkey_import((unsigned char*)begin(), &privkey[0], privkey.size()))
                                                                                          ^
key.cpp: In member function ‘bool CPubKey::VerifyCompact(const uint256&, const std::vector<unsigned char>&) const’:
key.cpp:631:10: warning: unused variable ‘fComp’ [-Wunused-variable]
     bool fComp = IsCompressed();
          ^
key.cpp: In member function ‘bool CPubKey::IsFullyValid() const’:
key.cpp:653:52: error: cannot convert ‘const unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ec_pubkey_verify(const secp256k1_context_t*, const unsigned char*, int)’
     if (!secp256k1_ec_pubkey_verify(begin(), size()))
                                                    ^
key.cpp: In member function ‘bool CPubKey::Decompress()’:
key.cpp:668:76: error: cannot convert ‘unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ec_pubkey_decompress(const secp256k1_context_t*, unsigned char*, int*)’
     int ret = secp256k1_ec_pubkey_decompress((unsigned char*)begin(), &clen);
                                                                            ^
key.cpp: In member function ‘bool CKey::Derive(CKey&, unsigned char*, unsigned int, const unsigned char*) const’:
key.cpp:710:84: error: cannot convert ‘unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ec_privkey_tweak_add(const secp256k1_context_t*, unsigned char*, const unsigned char*)’
     bool ret = secp256k1_ec_privkey_tweak_add((unsigned char*)keyChild.begin(), out);
                                                                                    ^
key.cpp: In member function ‘bool CPubKey::Derive(CPubKey&, unsigned char*, unsigned int, const unsigned char*) const’:
key.cpp:729:106: error: cannot convert ‘unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ec_pubkey_tweak_add(const secp256k1_context_t*, unsigned char*, int, const unsigned char*)’
     bool ret = secp256k1_ec_pubkey_tweak_add((unsigned char*)pubkeyChild.begin(), pubkeyChild.size(), out);
                                                                                                          ^
makefile.unix:201: recipe for target 'obj/key.o' failed
make: *** [obj/key.o] Error 1
make: *** Waiting for unfinished jobs....

[8-bit-Party]

You have cloned wrong branch (use -b fixed_sync).
Latest orig dev commit described as Tor updates /or something, fake anyway/ brought this crap you see.

[allZuckedUp]

You have cloned wrong branch (use -b fixed_sync).
Latest orig dev commit described as Tor updates /or something, fake anyway/ brought this crap you see.

I wish it were that easy... I git cloned via the following as per your posts...

git clone -b fixed_sync https://github.com/8bit-dev/8bit.git

[8-bit-Party]

Now you need downgraded secp256k1
Make sure that downgraded version will fully overwrite current one and remember about ldconfig.

[allZuckedUp]

Now you need downgraded secp256k1
Make sure that downgraded version will fully overwrite current one and remember about ldconfig.

I totally did... here's specifically what I did for secp256k1, it's exactly what works to compile the old wallet.

• git clone https://github.com/bitcoin/secp256k1.git
• cd secp256k1
• git checkout a1d5ae1
• ./autogen.sh
• ./configure
• make
• sudo make install
• sudo ldconfig

On one of the boxes it's failing to compile on, I JUST successfully compiled the old version of the 8bit wallet... Still can't compile the new code.

[8-bit-Party]

On one of the boxes it's failing to compile on, I JUST successfully compiled the old version of the 8bit wallet.

Which commit version you have successfully compiled?
01db6031e6506ac8d5779ec8a69889b1646b65de
or
bcf2b5f42f0b81dfe1e424f5aae96cdc44bbb794

[allZuckedUp]

On one of the boxes it's failing to compile on, I JUST successfully compiled the old version of the 8bit wallet.

Which commit version you have successfully compiled?
01db6031e6506ac8d5779ec8a69889b1646b65de
or
bcf2b5f42f0b81dfe1e424f5aae96cdc44bbb794

Ummm... e69cf314d9390babcbc91cf20e7b8b7d8aaace26

Isn't that the current "master"?

[8-bit-Party]

Yes it is - but it's in my repo. What about old but still official bitbucket repo? Does it compile on your box?