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.
Topic: [*] 8BIT [Dark Masternodes][Anon][Roadmap Stage 4] - page 117. (Read 379550 times)
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.
EDIT: Fixed
https://github.com/spencerlievens/8bit/commit/df2e0082bd579070de3481239c7d8d65dcb40e9dOK 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!
I have the WORST timing!
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.
EDIT: Fixed
https://github.com/spencerlievens/8bit/commit/df2e0082bd579070de3481239c7d8d65dcb40e9dOK 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!
Solving this first: GUI: QObject::connect: No such signal WalletModel::balanceChanged(qint64, qint64, qint64, qint64)
EDIT: Fixed https://github.com/8bit-dev/8bit/pull/2
OK next I am going to looking into this last error. Will post back.
EDIT: Fixed
https://github.com/8bit-dev/8bit/pull/2OK next I am going to looking into this last error. Will post back.
Happy labor day to the guys in the US
ProcessMessage(dseep, 116 bytes) FAILED
socket recv error 104
GUI: QCoreApplication::postEvent: Unexpected null receiver
GUI: QCoreApplication::postEvent: Unexpected null receiver
GUI: QCoreApplication::postEvent: Unexpected null receiver
GUI: QObject::connect: No such signal WalletModel::balanceChanged(qint64, qint64, qint64, qint64)
GUI: QObject::connect: (receiver name: 'SendCoinsDialog')
socket recv error 104
GUI: QCoreApplication::postEvent: Unexpected null receiver
GUI: QCoreApplication::postEvent: Unexpected null receiver
Has no one seen this output in debug.log previously?
socket recv error 104
GUI: QCoreApplication::postEvent: Unexpected null receiver
GUI: QCoreApplication::postEvent: Unexpected null receiver
GUI: QCoreApplication::postEvent: Unexpected null receiver
GUI: QObject::connect: No such signal WalletModel::balanceChanged(qint64, qint64, qint64, qint64)
GUI: QObject::connect: (receiver name: 'SendCoinsDialog')
socket recv error 104
GUI: QCoreApplication::postEvent: Unexpected null receiver
GUI: QCoreApplication::postEvent: Unexpected null receiver
Has no one seen this output in debug.log previously?
DarkSend GUI Fix, Seeds Added, Checkpoints Added, build-detect-platform permissions change & miniwget path error fixed.
https://github.com/8bit-dev/8bit/pull/1
Donations welcome for my work so far - 18msnkjeQJdZvNHVKQWoZo5z6EM2eqnnhE (BTC)
https://github.com/8bit-dev/8bit/pull/1
Donations welcome for my work so far - 18msnkjeQJdZvNHVKQWoZo5z6EM2eqnnhE (BTC)
Sorry for not being so active these past time, im surfacing some problems, but still trying to stay up to date with 8bit community
hi niki25. The Bitcredits dev (bitcreditscc) is currently working on an update to the 8BIT code, he can explain more. We also have the LimX dev and DarkSilk dev available to help if needed.
Hi, and thanks for the update, didnt know that
You also claimed "I spoke to Mullick a few days ago and everything is fine with Cryptsy / 8BIT " I ask you are you sure or are you a liar?
FUD then lol.
You also claimed "I spoke to Mullick a few days ago and everything is fine with Cryptsy / 8BIT " I ask you are you sure or are you a liar?
ps I dont fud and i dont own much 8bit only about 3k but it is funny there are alot of silly rabbits here.why would someone fud now?to buy cheaper? hehe not me!!
ps I dont fud and i dont own much 8bit only about 3k but it is funny there are alot of silly rabbits here.why would someone fud now?to buy cheaper? hehe not me!!
I spoke to Mullick a few days ago and everything is fine with Cryptsy / 8BIT, so you just made that up yourself
I have no idea why he would say that,he has a large backlog of confirmed withdraws that he has to send out manually now.Besides if you didnt know there was a problem then you are clearly out of the info loop and it makes me believe you just made that statement up.I have no idea why he would tell you a lie then tell me the truth?
I have no idea why he would say that,he has a large backlog of confirmed withdraws that he has to send out manually now.Besides if you didnt know there was a problem then you are clearly out of the info loop and it makes me believe you just made that statement up.I have no idea why he would tell you a lie then tell me the truth?
You are claiming Cryptsy are going to 'lock' the 8BIT wallet - i'm saying that's not true, unless you have a source, or are you just here to FUD?
I spoke to Mullick a few days ago and everything is fine with Cryptsy / 8BIT, so you just made that up yourself
I have no idea why he would say that,he has a large backlog of confirmed withdraws that he has to send out manually now.Besides if you didnt know there was a problem then you are clearly out of the info loop and it makes me believe you just made that statement up.I have no idea why he would tell you a lie then tell me the truth?
I have no idea why he would say that,he has a large backlog of confirmed withdraws that he has to send out manually now.Besides if you didnt know there was a problem then you are clearly out of the info loop and it makes me believe you just made that statement up.I have no idea why he would tell you a lie then tell me the truth?
Sorry for not being so active these past time, im surfacing some problems, but still trying to stay up to date with 8bit community
hi niki25. The Bitcredits dev (bitcreditscc) is currently working on an update to the 8BIT code, he can explain more. We also have the LimX dev and DarkSilk dev available to help if needed.
not 100percent sure but...can be traded on the exchange but they wont take deposits or withdraws until devs fix the wallet
ps confirmed withdraws that didnt make it to wallets will be paid tonite then wallet will be locked
ps confirmed withdraws that didnt make it to wallets will be paid tonite then wallet will be locked
I spoke to Mullick a few days ago and everything is fine with Cryptsy / 8BIT, so you just made that up yourself?
Sorry for not being so active these past time, im surfacing some problems, but still trying to stay up to date with 8bit community
not 100percent sure but...can be traded on the exchange but they wont take deposits or withdraws until devs fix the wallet
Ok thank you.
not 100percent sure but...can be traded on the exchange but they wont take deposits or withdraws until devs fix the wallet
ps confirmed withdraws that didnt make it to wallets will be paid tonite then wallet will be locked
ps confirmed withdraws that didnt make it to wallets will be paid tonite then wallet will be locked
well you heard it first from me.call me a liar all you want.give it 24hrs.then call me a liar
ps i didnt say it was to be delisted read my post.i said the wallet will be locked
ps i didnt say it was to be delisted read my post.i said the wallet will be locked
Being a non dev, would you please explain what a locked wallet does or provides?
Thanks so much!
well you heard it first from me.call me a liar all you want.give it 24hrs.then call me a liar
ps i didnt say it was to be delisted read my post.i said the wallet will be locked
ps i didnt say it was to be delisted read my post.i said the wallet will be locked
Ok, I'll wait 24 hours... Not a problem.
well you heard it first from me.call me a liar all you want.give it 24hrs.then call me a liar
ps i didnt say it was to be delisted read my post.i said the wallet will be locked
ps i didnt say it was to be delisted read my post.i said the wallet will be locked
Jump to: