Topic: BANKSYCOIN (SOON TO BE ARTSYCOIN) - ORIGINAL OFFICIAL THREAD - page 2. (Read 75801 times)
I hate to say it, but I agree. Wallet doesn't work and it looks like nothing is being done.. Another bag to hold!!
haha try again!
banksycoin was dead as soon as it got renamed to artsycoin.
obviously banksy is not artsy !
so it had to die.
shame for anyone who believed into it.
the dev team are officially the most dead team in crypto ever.
don't talk to zombies they only want your brain.
banksycoin was dead as soon as it got renamed to artsycoin.
obviously banksy is not artsy !
so it had to die.
shame for anyone who believed into it.
the dev team are officially the most dead team in crypto ever.
don't talk to zombies they only want your brain.
Is a new wallet out yet?
Seems like new devs are gone ...
Hope not forever ... but it seems like they are away from quite long time.
Kind regards.
Is a new wallet out yet?
How hard is it to be in Cryptsy? There are tons of crap coins there and it should be feasible for banksycoin to get in. Any new development???
Hello,
Any news about Artsycoin??? Seems very quiet...
Best regards.
Any news about Artsycoin??? Seems very quiet...
Best regards.
bump
Hello,
Any news about Artsycoin??? Seems very quiet...
Best regards.
Any news about Artsycoin??? Seems very quiet...
Best regards.
i'm seeing strange behaviour from my daemon.
start it up.
it is busy for a few minutes - high CPU /MEM usage and will not respond (this seems normal to previous behaviours)
once it's calmed down, to the point where previously it would respond.
it either
a) responds normally
b) responds once then shuts down. eg will give appropriate response to
Banksycoind getinfo
then shut down so next response will be "error: no response from server"
yet to capture anything from debug.log. it seems to be not doing this at the moment.
c) shuts down before responding. eg is running, upon a
Banksycoind listaddressgroupings
shuts down "error: no response from server"
there is nothing obvious in the debug.log and db.log is empty
debug ends with ->
>>> CheckStakeKernelHash: nTimeWeight = 5450902
>>> CheckStakeKernelHash: passed GetKernelStakeModifier
>>> bnCoinDayWeight = 33753, bnTargetPerCoinDay=298528506367175458951681909829523$
>>> CheckStakeKernelHash - hashProofOfStake too much
ThreadRPCServer method=listaddressgroupings
edit.
trying it with a new wallet.dat seems to have fixed it
start it up.
it is busy for a few minutes - high CPU /MEM usage and will not respond (this seems normal to previous behaviours)
once it's calmed down, to the point where previously it would respond.
it either
a) responds normally
b) responds once then shuts down. eg will give appropriate response to
Banksycoind getinfo
then shut down so next response will be "error: no response from server"
yet to capture anything from debug.log. it seems to be not doing this at the moment.
c) shuts down before responding. eg is running, upon a
Banksycoind listaddressgroupings
shuts down "error: no response from server"
there is nothing obvious in the debug.log and db.log is empty
debug ends with ->
>>> CheckStakeKernelHash: nTimeWeight = 5450902
>>> CheckStakeKernelHash: passed GetKernelStakeModifier
>>> bnCoinDayWeight = 33753, bnTargetPerCoinDay=298528506367175458951681909829523$
>>> CheckStakeKernelHash - hashProofOfStake too much
ThreadRPCServer method=listaddressgroupings
edit.
trying it with a new wallet.dat seems to have fixed it
Dear PICISI sponsor,
For a limited time PICISI is offering each PICISI sponsor a FREE article about their entity in relation to PICISI.
Please note that the story need not relate directly to crowdfunding, or cryptocurrency, the most important factor is an informative and compelling story, we will figure out how to include PICISI, Pi, and/or other essentials.
I invite you to take advantage of the opportunity to put your entity, you, or someone else related to your entity in the spotlight.
Contact me via PM or here: https://bitcointalksearch.org/topic/m.11312978
For a limited time PICISI is offering each PICISI sponsor a FREE article about their entity in relation to PICISI.
Please note that the story need not relate directly to crowdfunding, or cryptocurrency, the most important factor is an informative and compelling story, we will figure out how to include PICISI, Pi, and/or other essentials.
I invite you to take advantage of the opportunity to put your entity, you, or someone else related to your entity in the spotlight.
Contact me via PM or here: https://bitcointalksearch.org/topic/m.11312978
oh dear.
was the competition just a bit too much ?
hmm
for clarity Artsy coin will continue with currency code: BSY? That will not change?
thanks
http://bitcoinagile.com/27885D/digital-artwork-becomes-tradeable-scarce-on-the-bitcoin-block-chain-cryptocoinsnews_stream
tagging digital artwork onto the blockchain .. cutting edge
any news about artsy??
you first
Checked
Then buy some!!!
Checked
It may just be my client. I'm using 1.4, it could also be a timing issue.
Tranactions are created with other inputs, if you have to many inputs making up the transaction it can become to large.
Its is an issue that affects ALL wallets, and is worse if you have lost of tiny transactions or mined blocks
You can fix this by "dusting" or "defragmenting" your wallet.
1. Backup old wallet.dat and move to a safe location
2. start wallet so you get a new wallet.dat, record the address
3. swap the old wallet back and send all your coins to the new address (you may have to do a bunch of small transactions)
4. once you have moved all the coins to the new wallet, you can send them back to the original wallet in one transaction.
Now you wallet will just have one input to build transactions from
Thanks!!! Good to know!!
It may just be my client. I'm using 1.4, it could also be a timing issue.
Tranactions are created with other inputs, if you have to many inputs making up the transaction it can become to large.
Its is an issue that affects ALL wallets, and is worse if you have lost of tiny transactions or mined blocks
You can fix this by "dusting" or "defragmenting" your wallet.
1. Backup old wallet.dat and move to a safe location
2. start wallet so you get a new wallet.dat, record the address
3. swap the old wallet back and send all your coins to the new address (you may have to do a bunch of small transactions)
4. once you have moved all the coins to the new wallet, you can send them back to the original wallet in one transaction.
Now you wallet will just have one input to build transactions from
Jump to: