When I run from source its working fine, but when I try making the installer it says (after doing a lot of stuff)
File not found error [Errno 2] No such file or directory: 'C:\\counterpartyd_build\\bin\\exe.win-i386-3.3'
Also, where do I check the testnet XCP?
Topic: [ANN][XCP] Counterparty - Pioneering Peer-to-Peer Finance - Official Thread - page 612. (Read 1276933 times)
January 16, 2014, 05:31:39 PM
January 16, 2014, 05:18:05 PM
The fix for this is in one of my recent commits. Please pull from git and try again.
Everything working now again – thanks for the quick fix. January 16, 2014, 05:16:27 PM
Warning: You must use counterpartyd to send the BTC or the burn will not be recognized.
I am bit confused. Can I get XCP by sending funds to the unspendable address from blockchain.info wallet by these instructions? http://counterpartyd-build.readthedocs.org/en/latest/HowToBurn.html#blockchain-info-my-wallet
(I am seeing that now the warning is scratched, so I guess I can send funds from blockchain.info wallet using the instructions above)
January 16, 2014, 04:11:18 PM
Ouch -__-
I'd REALLY appreciate this time if you could upload the new database when your computer finish it in 30min.
It's very light, quickly done.
New database mean I cannot use your soft for yet another 36h with my 2GBram/crappy hardware.
I'd REALLY appreciate this time if you could upload the new database when your computer finish it in 30min.
It's very light, quickly done.
New database mean I cannot use your soft for yet another 36h with my 2GBram/crappy hardware.
A downloadable database would of course be convenient but how could you be sure that the source can be trusted?
If the dev upload it on their git page or on counterpartyd-build.readthedocs.org
It is enough for me now.
(to be 100% trusted: PhantomPhreak could post his PGP key here, sign everything, blablabla. Welcomed, but not necessary for now.
Just a quick upload in the next 12h & habit of updating it each time rebuild-from-start-is-needed)
January 16, 2014, 04:00:20 PM
I rebuilt the database and catched up with the last block. When trying to burn BTC I get this error now:
Code:
Traceback (most recent call last):
File "./counterpartyd.py", line 529, in
json_print(bitcoin.transmit(unsigned_tx_hex, unsigned=args.unsigned))
File "/Users/Max/counterpartyd/lib/bitcoin.py", line 298, in transmit
if ask and not is_api:
NameError: global name 'is_api' is not defined
File "./counterpartyd.py", line 529, in
json_print(bitcoin.transmit(unsigned_tx_hex, unsigned=args.unsigned))
File "/Users/Max/counterpartyd/lib/bitcoin.py", line 298, in transmit
if ask and not is_api:
NameError: global name 'is_api' is not defined
Same error occurs when attempting to issue.
I'm on it. Thanks.
The fix for this is in one of my recent commits. Please pull from git and try again.
January 16, 2014, 03:53:19 PM
I rebuilt the database and catched up with the last block. When trying to burn BTC I get this error now:
Code:
Traceback (most recent call last):
File "./counterpartyd.py", line 529, in
json_print(bitcoin.transmit(unsigned_tx_hex, unsigned=args.unsigned))
File "/Users/Max/counterpartyd/lib/bitcoin.py", line 298, in transmit
if ask and not is_api:
NameError: global name 'is_api' is not defined
File "./counterpartyd.py", line 529, in
json_print(bitcoin.transmit(unsigned_tx_hex, unsigned=args.unsigned))
File "/Users/Max/counterpartyd/lib/bitcoin.py", line 298, in transmit
if ask and not is_api:
NameError: global name 'is_api' is not defined
Same error occurs when attempting to issue.
I'm on it. Thanks.
January 16, 2014, 03:52:17 PM
I rebuilt the database and catched up with the last block. When trying to burn BTC I get this error now:
Code:
Traceback (most recent call last):
File "./counterpartyd.py", line 529, in
json_print(bitcoin.transmit(unsigned_tx_hex, unsigned=args.unsigned))
File "/Users/Max/counterpartyd/lib/bitcoin.py", line 298, in transmit
if ask and not is_api:
NameError: global name 'is_api' is not defined
File "./counterpartyd.py", line 529, in
json_print(bitcoin.transmit(unsigned_tx_hex, unsigned=args.unsigned))
File "/Users/Max/counterpartyd/lib/bitcoin.py", line 298, in transmit
if ask and not is_api:
NameError: global name 'is_api' is not defined
Same error occurs when attempting to issue.
January 16, 2014, 02:16:32 PM
I rebuilt the database and catched up with the last block. When trying to burn BTC I get this error now:
Code:
Traceback (most recent call last):
File "./counterpartyd.py", line 529, in
json_print(bitcoin.transmit(unsigned_tx_hex, unsigned=args.unsigned))
File "/Users/Max/counterpartyd/lib/bitcoin.py", line 298, in transmit
if ask and not is_api:
NameError: global name 'is_api' is not defined
File "./counterpartyd.py", line 529, in
json_print(bitcoin.transmit(unsigned_tx_hex, unsigned=args.unsigned))
File "/Users/Max/counterpartyd/lib/bitcoin.py", line 298, in transmit
if ask and not is_api:
NameError: global name 'is_api' is not defined
January 16, 2014, 01:15:17 PM
Ouch -__-
I'd REALLY appreciate this time if you could upload the new database when your computer finish it in 30min.
It's very light, quickly done.
New database mean I cannot use your soft for yet another 36h with my 2GBram/crappy hardware.
I'd REALLY appreciate this time if you could upload the new database when your computer finish it in 30min.
It's very light, quickly done.
New database mean I cannot use your soft for yet another 36h with my 2GBram/crappy hardware.
A downloadable database would of course be convenient but how could you be sure that the source can be trusted?
January 16, 2014, 12:43:23 PM
Ouch -__-
I'd REALLY appreciate this time if you could upload the new database when your computer finish it in 30min.
It's very light, quickly done.
New database mean I cannot use your soft for yet another 36h with my 2GBram/crappy hardware.
I'd REALLY appreciate this time if you could upload the new database when your computer finish it in 30min.
It's very light, quickly done.
New database mean I cannot use your soft for yet another 36h with my 2GBram/crappy hardware.
January 16, 2014, 12:28:42 PM
The fix is up.
I guess we have to rebuild the database for this to get effective, right?
Actually, I ended up altering the database schema not for this change (SQLite3 simply cannot do unsigned integers!), but for something unrelated (and actually rather unimportant---making the supported column of the transaction table a proper bool).
January 16, 2014, 12:25:19 PM
The fix is up.
I guess we have to rebuild the database for this to get effective, right?
January 16, 2014, 12:23:18 PM
Yes, my hackish solution from two days ago was off by one, and someone exploited that. I think that I've figured out the correct fix, however, but it requires a DB rebuild, so it'll be a few minutes before I can test it properly and push the commit.
Would appreciate if you can post a quick update once the commit has been pushed.
cheers
Sure. I'm still wrestling with SQLite3 and I have to go AFK for a couple of hours. I'll fix the problem soon!
The fix is up.
January 16, 2014, 12:08:19 PM
So is there any practical way to use the Bitcoin Qt wallet as .. an XCP wallet ?
It's created this way. All smooth.You burn BTC, XCP are created and linked to your pubkey in your BTC wallet.dat
--------
I'm impressed by the burn amount! 1114BTC O.o
Over 300 BTC (over 250'000$) since I last checked! went crazy fast.
Do we have a few heavy heavy burner? over 100 BTC?
I didn't check the transaction record.
I also got the OverflowError: Python int too large to convert to SQLite INTEGER (at block 280807)
I have to update, maybe it's already solved.
PhantomPhreak, may I ask own you manage to see that someone tried to create asset "NEXT" in block 280807?
Can average user also see these kind of thing?
I see nothing from blockchain.info
January 16, 2014, 10:19:11 AM
Yes, my hackish solution from two days ago was off by one, and someone exploited that. I think that I've figured out the correct fix, however, but it requires a DB rebuild, so it'll be a few minutes before I can test it properly and push the commit.
Would appreciate if you can post a quick update once the commit has been pushed.
cheers
Sure. I'm still wrestling with SQLite3 and I have to go AFK for a couple of hours. I'll fix the problem soon!
January 16, 2014, 10:12:40 AM
So is there any practical way to use the Bitcoin Qt wallet as .. an XCP wallet ?
January 16, 2014, 09:34:22 AM
It seems someone tried to create asset "NEXT" in block 280807:
https://blockchain.info/tx/acddcd5bc59349de709b0031e95c5610c233728548e8b308e32efb5d50385ee9
This asset was created with a very large quantity of 2^63 (9223372036854775808) which seems to cause this error.
https://blockchain.info/tx/acddcd5bc59349de709b0031e95c5610c233728548e8b308e32efb5d50385ee9
This asset was created with a very large quantity of 2^63 (9223372036854775808) which seems to cause this error.
Yes, my hackish solution from two days ago was off by one, and someone exploited that. I think that I've figured out the correct fix, however, but it requires a DB rebuild, so it'll be a few minutes before I can test it properly and push the commit.
[/quote]
Would appreciate if you can post a quick update once the commit has been pushed.
cheers
January 16, 2014, 09:33:44 AM
From what I'm seeing on Blockscan, the last 20 burns didn't go through.
They should go through once the bug issue reported earlier is fixed uploaded to git. So as long as you burnt them correctly with the instructions provided in this thread your should be good to go
Cheers
Hey MTBITCOIN ? Where do you see this project headed? I burned 5 BTC. You think I'm in a good spot ? I just have 2 other questions. Can you point me in the direction of understanding how to get Bitcoin-qt working with counterpartyd.... and will that help me consolidate my XCP ? Cause I have like.. 6,500ish XCP on 5 different BTC addresses. Thanks for any input!
January 16, 2014, 09:32:03 AM
Ok lemme delete my panic posts! Thanks! haha sorry noob here.
January 16, 2014, 09:31:35 AM
From what I'm seeing on Blockscan, the last 20 burns didn't go through.
They should go through once the bug issue reported earlier is fixed uploaded to git. So as long as you burnt them correctly with the instructions provided in this thread you should be good to go
Cheers
Jump to: