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

[SLievensDRKSLK]

Ah I was just asked to do the work and have been working.

I think the commits have been merged :/

Sorry that is out of my control. I just did a pull request.

Sorry.

[Tinkles]

Solving this first: GUI: QObject::connect: No such signal WalletModel::balanceChanged(qint64, qint64, qint64, qint64)

EDIT: Fixed https://github.com/spencerlievens/8bit/commit/df2e0082bd579070de3481239c7d8d65dcb40e9d

OK next. I am going to looking into this last error. Will post back.

Give it a minute if you would, I think a hard fork is about to be posted.

Not that we don't appreciate you, just don't want you doing a bunch of stuff that is already completed.

If you would post your 8bit Addy, I'm sure the community would hook u up with some.  Thanks!

This is correct, we actually have 2 NEW VERSIONs coming now lol

I have messaged BitCredits dev and asked him to check DRKSLK devs work and merge it with his (because he has been working already on this for a few days)

So for now, please just use this github for testing.

You wait for a new wallet...then 2 come at once  

[Tinkles]

Ah I was just asked to do the work and have been working.

I think the commits have been merged :/

Sorry that is out of my control. I just did a pull request.

Sorry.

Don't be sorry, just a minor mixup.  We really appreciate the work you did an 8BIT party merged it already.

I have asked BitCredits dev to merge your stuff with his so no work is lost here.

And you offered to be the full time 'support dev' for 8BIT, I think that's a great idea, you got my vote

[dbt1033]

Ah I was just asked to do the work and have been working.

I think the commits have been merged :/

Sorry that is out of my control. I just did a pull request.

Sorry.

Don't be sorry, just a minor mixup.  We really appreciate the work you did an 8BIT party merged it already.

I have asked BitCredits dev to merge your stuff with his so no work is lost here.

And you offered to be the full time 'support dev' for 8BIT, I think that's a great idea, you got my vote

Yeah Bitcreditscc can't be here full time, so if you'd like to stick around and work with him in the future, that would be awesome.

[SLievensDRKSLK]

Ah I was just asked to do the work and have been working.

I think the commits have been merged :/

Sorry that is out of my control. I just did a pull request.

Sorry.

Don't be sorry, just a minor mixup.  We really appreciate the work you did an 8BIT party merged it already.

I have asked BitCredits dev to merge your stuff with his so no work is lost here.

And you offered to be the full time 'support dev' for 8BIT, I think that's a great idea, you got my vote

Yeah Bitcreditscc can't be here full time, so if you'd like to stick around and work with him in the future, that would be awesome.

I have messaged BitCredits on Skype to explain.

[SLievensDRKSLK]

What is your testnet port?

[SLievensDRKSLK]

Nevermind I have it.

[SLievensDRKSLK]

I should be able to provide Mac wallets for this.

Can you guys get Windows wallets built?

[8-bit-Party]

gitian FTW

[SLievensDRKSLK]

3 pull requests to merge

https://github.com/8bit-dev/8bit/pull/2

https://github.com/8bit-dev/8bit/pull/3

https://github.com/8bit-dev/8bit/pull/4

There is still an error in debug that needs ironing out:

Misbehaving: 67.1.221.115:18888 (0 -> 1)
ProcessMessage(dseep, 116 bytes) FAILED
Misbehaving: 50.43.15.67:18888 (0 -> 1)
ProcessMessage(dseep, 116 bytes) FAILED
Misbehaving: 50.43.15.67:18888 (1 -> 2)
ProcessMessage(dsee, 253 bytes) FAILED
Misbehaving: 67.1.221.115:18888 (1 -> 2)
ProcessMessage(dsee, 253 bytes) FAILED

[allZuckedUp]

Solving this first: GUI: QObject::connect: No such signal WalletModel::balanceChanged(qint64, qint64, qint64, qint64)

EDIT: Fixed https://github.com/spencerlievens/8bit/commit/df2e0082bd579070de3481239c7d8d65dcb40e9d

OK next. I am going to looking into this last error. Will post back.

Give it a minute if you would, I think a hard fork is about to be posted.

Not that we don't appreciate you, just don't want you doing a bunch of stuff that is already completed.

If you would post your 8bit Addy, I'm sure the community would hook u up with some.  Thanks!

This is correct, we actually have 2 NEW VERSIONs coming now lol

I have messaged BitCredits dev and asked him to check DRKSLK devs work and merge it with his (because he has been working already on this for a few days)

So for now, please just use this github for testing.

You wait for a new wallet...then 2 come at once  

WOW! this is awesome!

OK, just to be clear, which github link is going to be the one?

[SLievensDRKSLK]

Solving this first: GUI: QObject::connect: No such signal WalletModel::balanceChanged(qint64, qint64, qint64, qint64)

EDIT: Fixed https://github.com/spencerlievens/8bit/commit/df2e0082bd579070de3481239c7d8d65dcb40e9d

OK next. I am going to looking into this last error. Will post back.

Give it a minute if you would, I think a hard fork is about to be posted.

Not that we don't appreciate you, just don't want you doing a bunch of stuff that is already completed.

If you would post your 8bit Addy, I'm sure the community would hook u up with some.  Thanks!

This is correct, we actually have 2 NEW VERSIONs coming now lol

I have messaged BitCredits dev and asked him to check DRKSLK devs work and merge it with his (because he has been working already on this for a few days)

So for now, please just use this github for testing.

You wait for a new wallet...then 2 come at once  

WOW! this is awesome!

OK, just to be clear, which github link is going to be the one?

I would assume - https://github.com/8bit-dev/8bit

[allZuckedUp]

I would assume - https://github.com/8bit-dev/8bit

okie dokie... seen a few links flying around and I'm just making sure.

Thanks, and welcome!!

[allZuckedUp]

FYI: When the new code becomes "official", and the fork is announced, I'm going to take down the faucet for a day or two while I upgrade the wallet and test it.

I'll do it as a cashout pushes, so it won't make a difference to anyone, other than being down for a bit.

[Tinkles]

I would assume - https://github.com/8bit-dev/8bit

okie dokie... seen a few links flying around and I'm just making sure.

Thanks, and welcome!!

yes that's the correct github: https://github.com/8bit-dev/8bit

[SLievensDRKSLK]

FYI: When the new code becomes "official", and the fork is announced, I'm going to take down the faucet for a day or two while I upgrade the wallet and test it.

I'll do it as a cashout pushes, so it won't make a difference to anyone, other than being down for a bit.

ATM there is no code change that will require a hardfork unless bitcredits does something. But as it stands the code on GitHub will not cause a fork.

[allZuckedUp]

FYI: When the new code becomes "official", and the fork is announced, I'm going to take down the faucet for a day or two while I upgrade the wallet and test it.

I'll do it as a cashout pushes, so it won't make a difference to anyone, other than being down for a bit.

ATM there is no code change that will require a hardfork unless bitcredits does something. But as it stands the code on GitHub will not cause a fork.

Cool... So nevermind then....

[Tinkles]

Ok, folks, sorry for the delay... But, I have indeed made this work with a slightly different revision of secp256k1...

Sooooo, without further adieu, here are the steps to build a linux wallet on a fresh debian jessie install (32 or 64).
Bare in mind, this is just for 8bitd, meaning no GUI, runs as a service.  (Better for nerds, because if you intend on things like running a bunch of masternodes on a single box, pretty pictures take up memory)
If there is enough demand, I'll see if I can cook up the QT recipe for everyone.

• 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 dh-autoreconf autotools-dev
• git clone https://github.com/bitcoin/secp256k1.git
• cd secp256k1
• git checkout d5b53aa81816214aa7c9e1095ff6ee1d4c13f9d2
• ./autogen.sh
• ./configure
• make
• sudo make install
• sudo ldconfig
• cd ..
• git clone -b fixed_sync https://github.com/8bit-dev/8bit.git
• cd 8bit/src/
• mkdir obj/crypto  <--- The need for this step is easy enough to fix in the code isn't it? :p
• make -f makefile.unix -j2 "USE_UPNP=-"
• strip -s 8bitd
• mv 8bitd <where ever you want it to live>
• mkdir ~/.8bit
• cd ~/.8bit
• wget http://www.8-bit.party/static/bootstrap.dat.bz2 && bunzip2 bootstrap.dat.bz2
• vi/nano 8bit.conf <-- And create file contents
• /path/to/./8bitd

Oh, and I speak from experience here, do NOT try to compile this on a system with less than 1G of RAM.... At least it didn't work out well for me.

Sooo, it's syncing now... and in the early going, it does indeed seem to be syncing the blockchain much faster... but I'm going to reserve all judgement on that until it finishes with the bootstrap file and has to pull from the network.

Code:

"version" : "v2.2.0.0-g"

Hey allZuckedUp.

I got Ubuntu setup today, is there any change to the above to compile now?  Should I remove the 'fixed_sync' branch from the git clone because we are on head now? (because i'm getting errors in key.cpp like missing variables  )

[SLievensDRKSLK]

Ok, folks, sorry for the delay... But, I have indeed made this work with a slightly different revision of secp256k1...

Sooooo, without further adieu, here are the steps to build a linux wallet on a fresh debian jessie install (32 or 64).
Bare in mind, this is just for 8bitd, meaning no GUI, runs as a service.  (Better for nerds, because if you intend on things like running a bunch of masternodes on a single box, pretty pictures take up memory)
If there is enough demand, I'll see if I can cook up the QT recipe for everyone.

• 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 dh-autoreconf autotools-dev
• git clone https://github.com/bitcoin/secp256k1.git
• cd secp256k1
• git checkout d5b53aa81816214aa7c9e1095ff6ee1d4c13f9d2
• ./autogen.sh
• ./configure
• make
• sudo make install
• sudo ldconfig
• cd ..
• git clone -b fixed_sync https://github.com/8bit-dev/8bit.git
• cd 8bit/src/
• mkdir obj/crypto  <--- The need for this step is easy enough to fix in the code isn't it? :p
• make -f makefile.unix -j2 "USE_UPNP=-"
• strip -s 8bitd
• mv 8bitd <where ever you want it to live>
• mkdir ~/.8bit
• cd ~/.8bit
• wget http://www.8-bit.party/static/bootstrap.dat.bz2 && bunzip2 bootstrap.dat.bz2
• vi/nano 8bit.conf <-- And create file contents
• /path/to/./8bitd

Oh, and I speak from experience here, do NOT try to compile this on a system with less than 1G of RAM.... At least it didn't work out well for me.

Sooo, it's syncing now... and in the early going, it does indeed seem to be syncing the blockchain much faster... but I'm going to reserve all judgement on that until it finishes with the bootstrap file and has to pull from the network.

Code:

"version" : "v2.2.0.0-g"

Hey allZuckedUp.

I got Ubuntu setup today, is there any change to the above to compile now?  Should I remove the 'fixed_sync' branch from the git clone because we are on head now? (because i'm getting errors in key.cpp like missing variables  )

People want to use the current code using my pull requests as they include all the seeds in IPv6 format plus checkpoints up to block 180000. I have also fixed the two GUI issues in the debug.log I have also enabled darksend on the overview page.

So yeah, use mine. Then I am sure bitcredits will apply his changes to the current code.

I also get instant connections with no conf file and also syncing with no blockchain bootstrap.

[SLievensDRKSLK]

If anyone wants to donate towards my work I now have an 8Bit address

8PFsve5YiqyBnN3VfNiwb6BhcYLVJCx8PE