Bitcoin Forum
September 23, 2019, 09:22:29 PM *
News: If you like a topic and you see an orange "bump" link, click it. More info.
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 [10] 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 ... 661 »
  Print  
Author Topic: [ANN][XCP] Counterparty - Pioneering Peer-to-Peer Finance - Official Thread  (Read 1267392 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
reader31
Full Member
***
Offline Offline

Activity: 221
Merit: 100


View Profile
January 04, 2014, 07:36:11 PM
 #181

cool thx Smiley will wait for the first confirmation.

Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1569273749
Hero Member
*
Offline Offline

Posts: 1569273749

View Profile Personal Message (Offline)

Ignore
1569273749
Reply with quote  #2

1569273749
Report to moderator
1569273749
Hero Member
*
Offline Offline

Posts: 1569273749

View Profile Personal Message (Offline)

Ignore
1569273749
Reply with quote  #2

1569273749
Report to moderator
1569273749
Hero Member
*
Offline Offline

Posts: 1569273749

View Profile Personal Message (Offline)

Ignore
1569273749
Reply with quote  #2

1569273749
Report to moderator
panonym
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250

Help and Love one another ♥


View Profile
January 04, 2014, 07:39:39 PM
 #182

Actual problem is that you will not be able to send those XCP anywhere.
Because for this to work on the mainnet, Eligius need to process your transaction.
Which it stopped.

counterpartyd address ADDRESS
So that at least is still working, with burn.
(I have to test by myself instead of asking the question...
But I'm curious and soft/hardware troube prevent me to test right now.)
Can I check the amount of XCP in any address with this command? Including not mine.
mtbitcoin
Legendary
*
Offline Offline

Activity: 876
Merit: 1000


Etherscan.io


View Profile
January 04, 2014, 07:42:38 PM
 #183

Actual problem is that you will not be able to send those XCP anywhere.
Because for this to work on the mainnet, Eligius need to process your transaction.
Which it stopped.

counterpartyd address ADDRESS
So that at least is still working, with burn.
(I have to test by myself instead of asking the question...
But I'm curious and soft/hardware troube prevent me to test right now.)
Can I check the amount of XCP in any address with this command? Including not mine.

Yes, you can  Smiley

Since everything is on the blockchain

Example output:


Balances
+-------+---------------+
| Asset |     Amount    |
+-------+---------------+
|  XCP  | 1479.70063636 |
+-------+---------------+

EtherScan::Ethereum Block Explorer | BlockScan::Coming Soon
FandangledGizmo
Legendary
*
Offline Offline

Activity: 1139
Merit: 1001


View Profile
January 04, 2014, 07:43:11 PM
 #184

Announcement: We made some changes to the protocol and the client: now burns don’t require the use of OP_RETURN, and we’re no longer pushing transactions through Eligius, which seems to now be rejecting anything with such an output. This means that 1) a bunch of bugs have been fixed, 2) the only Counterparty transaction that will work on mainnet until Bitcoind 0.9 comes out is a burn, 3) burns are much faster, and 4) it is theoretically possible for burns to be made with a regular Bitcoin client.

We’re not currently recommending that anyone use anything other than counterpartyd to burn. The format of a Counterparty transaction
is very specific, and we can’t guarantee that a transaction constructed by any other software will work (and if it doesn’t, you’ll lose your BTC).

For those interested, the protocol will recognise as a valid burn any transaction with the following characteristics:
  • All of the input addresses are identical.
  • The address of the first output is the unspendable address '1CounterpartyXXXXXXXXXXXXXXXUWLpVr' (mainnet) or 'mvCounterpartyXXXXXXXXXXXXXXW24Hef' (testnet).
  • The total number of BTC burned by the source address is less than or equal to 1.

Instructions on how to use a Blockchain.info wallet to construct a burn should be forthcoming. The burn functionality of counterpartyd will continue to work as it has been doing, and of course previous burns remain valid.

+1. That would be great if you could send BTC from a blockchain.info wallet and receive XCP.

& thanks for answering my previous questions.
xibeijan
Legendary
*
Offline Offline

Activity: 1218
Merit: 1000


View Profile
January 04, 2014, 07:44:06 PM
 #185

Have the instructions for how to burn on blockchain.info been posted yet?

Notable projects 2019: Semux, Dero, Wagerr, BEAM
sixteendigits
Sr. Member
****
Offline Offline

Activity: 462
Merit: 250


View Profile
January 04, 2014, 07:48:56 PM
 #186

Very interested, after the success of NXT, this is the only 2nd gen crypto that doesn't scream scam to me.  But yeah, please come up with a simplified (ie. idiot proof) way to invest because I am scared I am going to screw something up and lose my BTC.
FandangledGizmo
Legendary
*
Offline Offline

Activity: 1139
Merit: 1001


View Profile
January 04, 2014, 07:56:08 PM
 #187

Only Mastercoin funding is centralized, protocol itself isn't centralized.

This isn't the place to discuss Mastercoin, but it may be worth pointing out an important difference here between Mastercoin's protocol and Counterparty's: every Mastercoin transaction has to have a small output to the Exodus Address (to which at least J.R. holds the private key). Counterparty has no such limitation.

EDIT: typo

Q1. I know you said this isn't the place to discuss MSC, but is the above true? Do you mean every future MSC transaction, (even once it's up & running) will have a small output to the Exodus address? That sucks.

Q2. As much as I like your POB decentralisation and I really do. Maintaining & further developing something like this will require serious funding? No? We can't expect you guys to do all the work when you're getting the same risk/reward incentive as us. Even Protoshares are now issuing Angel shares as they need more direct funding. (Or maybe they're just scamming, we'll have to see if they actually release their delayed Keyhotee soon.)
xibeijan
Legendary
*
Offline Offline

Activity: 1218
Merit: 1000


View Profile
January 04, 2014, 07:56:25 PM
 #188

Can anyone help with this error I'm getting?

./counterpartyd.py server

I get.

Traceback (most recent call last):
  File "./counterpartyd.py", line 405, in <module>
    util.bitcoind_check(db)
  File "/home/X/counterpartyd/lib/util.py", line 18, in bitcoind_check
    block_count = bitcoin.rpc('getblockcount', [])
  File "/home/X/counterpartyd/lib/bitcoin.py", line 36, in rpc
    response = requests.post(config.RPC, data=json.dumps(payload), headers=headers)
  File "/usr/lib/python3/dist-packages/requests/api.py", line 85, in post
    return request('post', url, data=data, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/api.py", line 40, in request
    return s.request(method=method, url=url, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 229, in request
    r.send(prefetch=prefetch)
  File "/usr/lib/python3/dist-packages/requests/models.py", line 468, in send
    url = self.full_url
  File "/usr/lib/python3/dist-packages/requests/models.py", line 382, in full_url
    netloc = netloc.encode('idna').decode('utf-8')
  File "/usr/lib/python3.2/encodings/idna.py", line 167, in encode
    result.extend(ToASCII(label))
  File "/usr/lib/python3.2/encodings/idna.py", line 73, in ToASCII
    raise UnicodeError("label empty or too long")
UnicodeError: label empty or too long

Notable projects 2019: Semux, Dero, Wagerr, BEAM
PhantomPhreak
Sr. Member
****
Offline Offline

Activity: 476
Merit: 250

Counterparty Chief Scientist and Co-Founder


View Profile
January 04, 2014, 08:02:09 PM
 #189

Have the instructions for how to burn on blockchain.info been posted yet?

No, not yet.
cityglut
Full Member
***
Offline Offline

Activity: 216
Merit: 100


View Profile
January 04, 2014, 08:07:30 PM
 #190

Only Mastercoin funding is centralized, protocol itself isn't centralized.

This isn't the place to discuss Mastercoin, but it may be worth pointing out an important difference here between Mastercoin's protocol and Counterparty's: every Mastercoin transaction has to have a small output to the Exodus Address (to which at least J.R. holds the private key). Counterparty has no such limitation.

EDIT: typo

Q1. I know you said this isn't the place to discuss MSC, but is the above true? Do you mean every future MSC transaction, (even once it's up & running) will have a small output to the Exodus address? That sucks.

Yes, it is true.

Q2. As much as I like your POB decentralisation and I really do. Maintaining & further developing something like this will require serious funding? No? We can't expect you guys to do all the work when you're getting the same risk/reward incentive as us. Even Protoshares are now issuing Angel shares as they need more direct funding. (Or maybe they're just scamming, we'll have to see if they actually release their delayed Keyhotee soon.)

While we do appreciate donations, it may be worth pointing out that Bitcoin's development was not predicated on outside funding, and Counterparty is: 1) much simpler and smaller project than Bitcoin, and 2) relatively full-featured.

Most open-source projects are community-driven, with software developers contributing not primarily for the financial incentives, but because they really believe in the project they are developing (Gavin Andresen, for example, worked on Bitcoin a long time before being hired full-time). I will certainly be investing in Counterparty, but this is because I think it is a great project with lots of potential, not because there is a lot of money in alt-coins at the moment.
xibeijan
Legendary
*
Offline Offline

Activity: 1218
Merit: 1000


View Profile
January 04, 2014, 08:09:36 PM
 #191

Have the instructions for how to burn on blockchain.info been posted yet?

No, not yet.

The instructions on the second post in this thread seem to indicate for us to use bitcoind.  Is that safe?  Does make sure all of the input addresses are identical?

Here's what I've done.

Setup bitcoin with the following config

Quote
rpcuser=bitcoinrpc
rpcpassword=yo
txindex=1
server=1

Quote
git clone https://github.com/PhantomPhreak/counterpartyd.git
cd counterpartyd
git describe
v0.1-17-g3bc6a3d

cat ~/.config/counterpartyd/counterpartyd.conf
[Default]
rpc-connect=localhost
rpc-port=8332
rpc-user=bitcoinrpc
rpc-password=yo

./counterpartyd.py server

Then I get

Quote
Traceback (most recent call last):
  File "./counterpartyd.py", line 405, in <module>
    util.bitcoind_check(db)
  File "/home/X/counterpartyd/lib/util.py", line 18, in bitcoind_check
    block_count = bitcoin.rpc('getblockcount', [])
  File "/home/X/counterpartyd/lib/bitcoin.py", line 36, in rpc
    response = requests.post(config.RPC, data=json.dumps(payload), headers=headers)
  File "/usr/lib/python3/dist-packages/requests/api.py", line 85, in post
    return request('post', url, data=data, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/api.py", line 40, in request
    return s.request(method=method, url=url, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 229, in request
    r.send(prefetch=prefetch)
  File "/usr/lib/python3/dist-packages/requests/models.py", line 468, in send
    url = self.full_url
  File "/usr/lib/python3/dist-packages/requests/models.py", line 382, in full_url
    netloc = netloc.encode('idna').decode('utf-8')
  File "/usr/lib/python3.2/encodings/idna.py", line 167, in encode
    result.extend(ToASCII(label))
  File "/usr/lib/python3.2/encodings/idna.py", line 73, in ToASCII
    raise UnicodeError("label empty or too long")
UnicodeError: label empty or too long

Notable projects 2019: Semux, Dero, Wagerr, BEAM
wizzardTim
Legendary
*
Offline Offline

Activity: 1708
Merit: 1000


Reality is stranger than fiction


View Profile
January 04, 2014, 08:11:12 PM
 #192

Have the instructions for how to burn on blockchain.info been posted yet?

No, not yet.

The instructions on the second post in this thread seem to indicate for us to use bitcoind.  Is that safe?  Does make sure all of the input addresses are identical?

Here's what I've done.

Setup bitcoin with the following config

Quote
rpcuser=bitcoinrpc
rpcpassword=yo
txindex=1
server=1

Quote
git clone https://github.com/PhantomPhreak/counterpartyd.git
cd counterpartyd
git describe
v0.1-17-g3bc6a3d

cat ~/.config/counterpartyd/counterpartyd.conf
[Default]
rpc-connect=localhost
rpc-port=8332
rpc-user=bitcoinrpc
rpc-password=yo

./counterpartyd.py server

Then I get

Quote
Traceback (most recent call last):
  File "./counterpartyd.py", line 405, in <module>
    util.bitcoind_check(db)
  File "/home/X/counterpartyd/lib/util.py", line 18, in bitcoind_check
    block_count = bitcoin.rpc('getblockcount', [])
  File "/home/X/counterpartyd/lib/bitcoin.py", line 36, in rpc
    response = requests.post(config.RPC, data=json.dumps(payload), headers=headers)
  File "/usr/lib/python3/dist-packages/requests/api.py", line 85, in post
    return request('post', url, data=data, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/api.py", line 40, in request
    return s.request(method=method, url=url, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 229, in request
    r.send(prefetch=prefetch)
  File "/usr/lib/python3/dist-packages/requests/models.py", line 468, in send
    url = self.full_url
  File "/usr/lib/python3/dist-packages/requests/models.py", line 382, in full_url
    netloc = netloc.encode('idna').decode('utf-8')
  File "/usr/lib/python3.2/encodings/idna.py", line 167, in encode
    result.extend(ToASCII(label))
  File "/usr/lib/python3.2/encodings/idna.py", line 73, in ToASCII
    raise UnicodeError("label empty or too long")
UnicodeError: label empty or too long

the bitcoin.conf shouldn't have daemon=1?

Behold the Tangle Mysteries! Dare to know It's truth.

- Excerpt from the IOTA Sacred Texts Vol. I
xibeijan
Legendary
*
Offline Offline

Activity: 1218
Merit: 1000


View Profile
January 04, 2014, 08:16:42 PM
 #193

Quote
the bitcoin.conf shouldn't have daemon=1?

You don't need this if you run bitcoind with -daemon, but I left that bit out.

Notable projects 2019: Semux, Dero, Wagerr, BEAM
PhantomPhreak
Sr. Member
****
Offline Offline

Activity: 476
Merit: 250

Counterparty Chief Scientist and Co-Founder


View Profile
January 04, 2014, 08:18:20 PM
 #194

Have the instructions for how to burn on blockchain.info been posted yet?

No, not yet.

The instructions on the second post in this thread seem to indicate for us to use bitcoind.  Is that safe?  Does make sure all of the input addresses are identical?

Here's what I've done.

Setup bitcoin with the following config

Quote
rpcuser=bitcoinrpc
rpcpassword=yo
txindex=1
server=1

Quote
git clone https://github.com/PhantomPhreak/counterpartyd.git
cd counterpartyd
git describe
v0.1-17-g3bc6a3d

cat ~/.config/counterpartyd/counterpartyd.conf
[Default]
rpc-connect=localhost
rpc-port=8332
rpc-user=bitcoinrpc
rpc-password=yo

./counterpartyd.py server

Then I get

Quote
Traceback (most recent call last):
  File "./counterpartyd.py", line 405, in <module>
    util.bitcoind_check(db)
  File "/home/X/counterpartyd/lib/util.py", line 18, in bitcoind_check
    block_count = bitcoin.rpc('getblockcount', [])
  File "/home/X/counterpartyd/lib/bitcoin.py", line 36, in rpc
    response = requests.post(config.RPC, data=json.dumps(payload), headers=headers)
  File "/usr/lib/python3/dist-packages/requests/api.py", line 85, in post
    return request('post', url, data=data, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/api.py", line 40, in request
    return s.request(method=method, url=url, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 229, in request
    r.send(prefetch=prefetch)
  File "/usr/lib/python3/dist-packages/requests/models.py", line 468, in send
    url = self.full_url
  File "/usr/lib/python3/dist-packages/requests/models.py", line 382, in full_url
    netloc = netloc.encode('idna').decode('utf-8')
  File "/usr/lib/python3.2/encodings/idna.py", line 167, in encode
    result.extend(ToASCII(label))
  File "/usr/lib/python3.2/encodings/idna.py", line 73, in ToASCII
    raise UnicodeError("label empty or too long")
UnicodeError: label empty or too long

the bitcoin.conf shouldn't have daemon=1?


Those instructions are for using Bitcoind as the backend for counterpartyd, and then using counterpartyd to burn (entirely safely), not for using Bitcoind to burn BTC directly (which would, at this time, be unsafe).

xnova, when he gets back online soon, should be able to help fix that bug you and a few others are having. I don't think that the daemon=1 option is the problem.
xibeijan
Legendary
*
Offline Offline

Activity: 1218
Merit: 1000


View Profile
January 04, 2014, 08:19:20 PM
 #195

Have the instructions for how to burn on blockchain.info been posted yet?

No, not yet.

The instructions on the second post in this thread seem to indicate for us to use bitcoind.  Is that safe?  Does make sure all of the input addresses are identical?

Here's what I've done.

Setup bitcoin with the following config

Quote
rpcuser=bitcoinrpc
rpcpassword=yo
txindex=1
server=1

Quote
git clone https://github.com/PhantomPhreak/counterpartyd.git
cd counterpartyd
git describe
v0.1-17-g3bc6a3d

cat ~/.config/counterpartyd/counterpartyd.conf
[Default]
rpc-connect=localhost
rpc-port=8332
rpc-user=bitcoinrpc
rpc-password=yo

./counterpartyd.py server

Then I get

Quote
Traceback (most recent call last):
  File "./counterpartyd.py", line 405, in <module>
    util.bitcoind_check(db)
  File "/home/X/counterpartyd/lib/util.py", line 18, in bitcoind_check
    block_count = bitcoin.rpc('getblockcount', [])
  File "/home/X/counterpartyd/lib/bitcoin.py", line 36, in rpc
    response = requests.post(config.RPC, data=json.dumps(payload), headers=headers)
  File "/usr/lib/python3/dist-packages/requests/api.py", line 85, in post
    return request('post', url, data=data, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/api.py", line 40, in request
    return s.request(method=method, url=url, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 229, in request
    r.send(prefetch=prefetch)
  File "/usr/lib/python3/dist-packages/requests/models.py", line 468, in send
    url = self.full_url
  File "/usr/lib/python3/dist-packages/requests/models.py", line 382, in full_url
    netloc = netloc.encode('idna').decode('utf-8')
  File "/usr/lib/python3.2/encodings/idna.py", line 167, in encode
    result.extend(ToASCII(label))
  File "/usr/lib/python3.2/encodings/idna.py", line 73, in ToASCII
    raise UnicodeError("label empty or too long")
UnicodeError: label empty or too long

the bitcoin.conf shouldn't have daemon=1?


Those instructions are for using Bitcoind as the backend for counterpartyd, and then using counterpartyd to burn (entirely safely), not for using Bitcoind to burn BTC directly (which would, at this time, be unsafe).

xnova, when he gets back online soon, should be able to help fix that bug you and a few others are having. I don't think that the daemon=1 option is the problem.

Thanks.  Who else if having that bug?  Maybe I could speak with them to see if they got anywhere with it.


Notable projects 2019: Semux, Dero, Wagerr, BEAM
konfet
Member
**
Offline Offline

Activity: 70
Merit: 10


View Profile
January 04, 2014, 08:27:03 PM
 #196

got the next errors on windows 7 x64 after updating to the newest source
Code:
C:\Python33\python.exe c:\counterpartyd_build\run.py --log-file=- -v

2014-01-05-T12:20:55\xcc\xee\xf1\xea\xee\xe2\xf1\xea\xee\xe5 \xe2\xf0\xe5\xec\xf
f (\xe7\xe8\xec\xe0) Starting new HTTP connection (1): 89.208.112.132
2014-01-05-T12:20:55\xcc\xee\xf1\xea\xee\xe2\xf1\xea\xee\xe5 \xe2\xf0\xe5\xec\xf
f (\xe7\xe8\xec\xe0) "POST http://rpc:rpcpw1234@localhost:18332/ HTTP/1.1" 404 7
14
Traceback (most recent call last):
  File "C:\Python33\Lib\json\decoder.py", line 368, in raw_decode
    obj, end = self.scan_once(s, idx)
StopIteration

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "c:\counterpartyd_build\dist\counterpartyd\counterpartyd.py", line 405, i
n <module>
    util.bitcoind_check(db)
  File "c:\counterpartyd_build\dist\counterpartyd\lib\util.py", line 18, in bitc
oind_check
    block_count = bitcoin.rpc('getblockcount', [])
  File "c:\counterpartyd_build\dist\counterpartyd\lib\bitcoin.py", line 45, in r
pc
    response_json = response.json()
  File "c:\counterpartyd_build\env\lib\requests\models.py", line 733, in json
    return json.loads(self.text, **kwargs)
  File "C:\Python33\Lib\json\__init__.py", line 319, in loads
    return _default_decoder.decode(s)
  File "C:\Python33\Lib\json\decoder.py", line 352, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "C:\Python33\Lib\json\decoder.py", line 370, in raw_decode
    raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
in browser on http://rpc:rpcpw1234@localhost:18332 got
Code: (google chrome)
{"result":null,"error":{"code":-32700,"message":"Parse error"},"id":null}
my bitcoin.conf and counterpartyd.conf are next:
Code: (bitcoin.conf)
rpcuser=rpc
rpcpassword=rpcpw1234
server=1
daemon=1
txindex=1
testnet=1

Code: (counterpartyd.conf)
[Default]
rpc-connect=localhost
rpc-port=18332
rpc-user=rpc
rpc-password=rpcpw1234
testnet=1

BTC: 19d14r8F932Khc2xDZeC4hvdmCF7q95SGW  LTC: LbzSRezSSs3eXP4rPor8wo8HJqgkrfC6f7  NMC: N8CFY5QaYRpQXq6LYQdSJqLuFGBqvSp6ua 
DVC: 14ZktX8LvnmSfcZKBgJrXfTTV8TpTQp4d5  QRK: QRb6v9RXACJut6GfDs7mcttdT7dTDcUZSK  WDC: WST6mDQELMhRmAQSdEfNNBUjEhRgqEsj9R
Cheap G\Hashes. With CoinBase, CampBX, Bter, Crypto-trade, Coins-e, Cryptsy you can easy save and increase your money. Please help poor sick developer.
PhantomPhreak
Sr. Member
****
Offline Offline

Activity: 476
Merit: 250

Counterparty Chief Scientist and Co-Founder


View Profile
January 04, 2014, 08:30:01 PM
 #197


Thanks.  Who else if having that bug?  Maybe I could speak with them to see if they got anywhere with it.


Sorry, my mistake. I thought that I had seen another person with that same problem.
xibeijan
Legendary
*
Offline Offline

Activity: 1218
Merit: 1000


View Profile
January 04, 2014, 08:41:35 PM
 #198

I seem to have fixed the issue.

I ran ./counterpartyd.py market

and I get

lib.exceptions.DatabaseError: Countparty database is behind Bitcoind.

Is that normal?

Looks like it's synchronising.

How can I check the status?

Thanks.

Notable projects 2019: Semux, Dero, Wagerr, BEAM
xibeijan
Legendary
*
Offline Offline

Activity: 1218
Merit: 1000


View Profile
January 04, 2014, 08:53:10 PM
 #199

I got another crash...

Quote
./counterpartyd.py -v --log-file=yo.log server


Traceback (most recent call last):
  File "./counterpartyd.py", line 532, in <module>
    blocks.follow()
  File "/home/X/counterpartyd/lib/blocks.py", line 390, in follow
    source, destination, btc_amount, fee, data = get_tx_info(tx)
  File "/home/X/counterpartyd/lib/blocks.py", line 319, in get_tx_info
    data = binascii.unhexlify(asm[1])
TypeError: 'str' does not support the buffer interface

Notable projects 2019: Semux, Dero, Wagerr, BEAM
btc4ever
Sr. Member
****
Offline Offline

Activity: 321
Merit: 250


View Profile
January 04, 2014, 09:02:07 PM
 #200

Is there any way (command) to gauge progress as counterpartyd is processing the blockchain?

Quote
$ ./counterpartyd.py  --rpc-password=$BTCPASS market
Traceback (most recent call last):
  File "./counterpartyd.py", line 407, in <module>
    util.database_check(db)
  File "/home/counterpartycoin/counterpartyd/lib/util.py", line 36, in database_check
    raise exceptions.DatabaseError('Countparty database is behind Bitcoind.')
lib.exceptions.DatabaseError: Countparty database is behind Bitcoind.

Psst!!  Wanna make bitcoin unstoppable? Why the Only Real Way to Buy Bitcoins Is on the Streets. Avoid banks and centralized exchanges.   Buy/Sell coins locally.  Meet other bitcoiners and develop your network.   Try localbitcoins.com or find or start a buttonwood / satoshi square in your area.  Pass it on!
Pages: « 1 2 3 4 5 6 7 8 9 [10] 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 ... 661 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!