Author

Topic: [ANN][XCP] Counterparty - Pioneering Peer-to-Peer Finance - Official Thread - page 622. (Read 1276933 times)

sr. member
Activity: 390
Merit: 254
Counterparty Developer
We may need to switch to destroying coins by sending them to an unspendable address.

By the way, any way to verify this?

Here's the quote from the first page of the project.

To get a rough idea of how many BTC have been burned so far, see https://blockchain.info/address/1CounterpartyXXXXXXXXXXXXXXXUWLpVr. Note that this page may show some false positives. You cannot just send bitcoins to that address with any client and expect to have them be properly burned. For more instructions on how to burn, e.g. with a Blockchain.info wallet, see Read The Docs.

Also, see www.blockscan.com
newbie
Activity: 29
Merit: 0
We may need to switch to destroying coins by sending them to an unspendable address.

By the way, any way to verify this?

Here's the quote from the first page of the project.

To get a rough idea of how many BTC have been burned so far, see https://blockchain.info/address/1CounterpartyXXXXXXXXXXXXXXXUWLpVr. Note that this page may show some false positives. You cannot just send bitcoins to that address with any client and expect to have them be properly burned. For more instructions on how to burn, e.g. with a Blockchain.info wallet, see Read The Docs.
sr. member
Activity: 390
Merit: 254
Counterparty Developer
The transaction seemed to go through, but I am stuck with Status: 0/unconfirmed without any broadcasts for about 20 minutes so far. Bitcoin-qt is well connected (10 active connections). How long does it take typically?
It did actually go through, though not for 30 minutes.


Also, more error reports:

1. rpc-user and rpc-password should be prefixed with "bitcoind-" in the autogenerated config from the installer. Or at least make that part of it clear.
2. I still get the u2026 unicode errors in windows when doing "counterpartyd market".

Open Orders
Traceback (most recent call last):
  File "counterpartyd.py", line 608, in
    market(args.give_asset, args.get_asset)
  File "counterpartyd.py", line 41, in market
    print(str(table.get_string(sortby='Price')))
  File "c:\Python33\lib\encodings\cp437.py", line 19, in encode
    return codecs.charmap_encode(input,self.errors,encoding_map)[0]
UnicodeEncodeError: 'charmap' codec can't encode character '\u2026' in position
483: character maps to

This worked before (albeit being blank), so obviously some of the new transactions that have come up in the last day are causing this error.

Thanks for these bug reports! Installer has been updated (new windows binary is available), and this unicode bug should have been fixed. Thanks.
hero member
Activity: 756
Merit: 502
We may need to switch to destroying coins by sending them to an unspendable address.

By the way, any way to verify this?
newbie
Activity: 29
Merit: 0
Good question: What would you need to build a DAC on Counterparty? This would be helpful to note here.

You are one of the core dev's? I'd like to PM then.

Not a core dev so you may wish to wait until they are online and you can PM them your details.
legendary
Activity: 1708
Merit: 1000
Reality is stranger than fiction
So, the new windows installer just creates the .exe in Program Files directory?

No longer need to run the run.py script?


I had the previous version of the installer and now installed the new. I ran the .exe and the whole db is downloaded again from the start! Why?
hero member
Activity: 756
Merit: 502
Good question: What would you need to build a DAC on Counterparty? This would be helpful to note here.

You are one of the core dev's? I'd like to PM then.
newbie
Activity: 29
Merit: 0
  • User-Created Assets: Issue user‐defined currencies/assets and pay dividends on them. You may now issue user-defined currencies/assets on Counterparty using mainnet.

So it means we can build DAC's on this right now? Any API upcoming?

Good question: What would you need to build a DAC on Counterparty? This would be helpful to note here.
hero member
Activity: 756
Merit: 502
  • User-Created Assets: Issue user‐defined currencies/assets and pay dividends on them. You may now issue user-defined currencies/assets on Counterparty using mainnet.

So it means we can build DAC's on this right now? Any API upcoming?
newbie
Activity: 29
Merit: 0
Did everyone see this announcement?

Are there questions about what was launched on yesterday?

Yep, will appreciate that in layman terms.

Yes. it means that Counterparty no longer needs to wait on Bitcoin

I can confirm that pretty much everything (sending, receiving, orders, issuance) is working. (I've been busy as you can see on blockscan.com).

Nice. Maybe it's time to start a new P2P Dice application...
sr. member
Activity: 364
Merit: 264
If people want to provide their addresses, I want to test transactions by sending them some TEST (lol). Until my bitcoins run out from all the fees ... lol.

BTC/XCP tips appreciated.

If you want to send some test coins, you are most welcomed   Cheesy

1L5dKm5ftLfiMBjq3yZDJMgr365J5SHkUC

Here you go, have some TEST :p

C:\Program Files\counterpartyd>counterpartyd address 1L5dKm5ftLfiMBjq3yZDJMgr365J5SHkUC
Balances
+-------+--------+
| Asset | Amount |
+-------+--------+
|  BTC  |  Huh   |
|  TEST |   50   |
+-------+--------+

Did everyone see this announcement?

Are there questions about what was launched on yesterday?

Yep, will appreciate that in layman terms.

Yes. it means that Counterparty no longer needs to wait on Bitcoin 0.9. You can now do the following and mainnet with the XCP you received after you burned your BTC. It is possible to start using Counterparty protocol features as they were outlined at the launch on January 2nd.

The following features are implemented and (mostly) working:
  • Send: XCP or user-created assets using mainnet, right this very moment.
  • User-Created Assets: Issue user‐defined currencies/assets and pay dividends on them. You may now issue user-defined currencies/assets on Counterparty using mainnet.
  • Distributed Exchange: Trade XCP, BTC or any asset with any other. Although there's no GUI as yet, you may now trade assets, on mainnet, using Counterparty.
  • Betting, Financial Derivatives: Make bets, or construct contracts for difference, on the numerical value of a feed. You may now construct, make bets or do the same with contracts on the numerical value of a feed.

NOTE: There is no need to wait for Eligius or for Bitcoin v 0.9. if you wish to start building your applications and using them on mainnet, you can do so.


I can confirm that pretty much everything (sending, receiving, orders, issuance) is working. (I've been busy as you can see on blockscan.com).
newbie
Activity: 29
Merit: 0
Did everyone see this announcement?

Are there questions about what was launched on yesterday?

Yep, will appreciate that in layman terms.

Yes. it means that Counterparty no longer needs to wait on Bitcoin 0.9. You can now do the following and mainnet with the XCP you received after you burned your BTC. It is possible to start using Counterparty protocol features as they were outlined at the launch on January 2nd.

The following features are implemented and (mostly) working:
  • Send: XCP or user-created assets using mainnet, right this very moment.
  • User-Created Assets: Issue user‐defined currencies/assets and pay dividends on them. You may now issue user-defined currencies/assets on Counterparty using mainnet.
  • Distributed Exchange: Trade XCP, BTC or any asset with any other. Although there's no GUI as yet, you may now trade assets, on mainnet, using Counterparty.
  • Betting, Financial Derivatives: Make bets, or construct contracts for difference, on the numerical value of a feed. You may now construct, make bets or do the same with contracts on the numerical value of a feed.

NOTE: There is no need to wait for Eligius or for Bitcoin v 0.9. if you wish to start building your applications and using them on mainnet, you can do so.
hero member
Activity: 756
Merit: 502
Did everyone see this announcement?

Are there questions about what was launched on yesterday?

Yep, will appreciate that in layman terms.
newbie
Activity: 29
Merit: 0
Announcement: We've added to Counterparty the ability to imbed and parse data in multi-signature outputs, in addition to OP_RETURNs. This means that all message types (not just burns) now work on mainnet, at regular speed. Counterparty is fully operational (like the second Death Star), without Eligius and without Bitcoin 0.9.

When OP_RETURN goes live, the multi-sig method will probably be retired, just because it's not officially supported and is slightly less elegant. However, the Bitcoin developers have (counter-productively) decided to allow only one OP_RETURN output per tx, so without multi-sig we are limited to 80 bytes per tx. With multi-sig, the limit is much higher. (N.B. Both methods may be combined in a single transaction.)

counterpartyd will continue to function as it always has, except now everything will actually work. As always, be careful: this software is still largely untested.

Did everyone see this announcement?

Are there questions about what was launched on yesterday?
legendary
Activity: 876
Merit: 1000
Etherscan.io
If people want to provide their addresses, I want to test transactions by sending them some TEST (lol). Until my bitcoins run out from all the fees ... lol.

BTC/XCP tips appreciated.

If you want to send some test coins, you are most welcomed   Cheesy

1L5dKm5ftLfiMBjq3yZDJMgr365J5SHkUC
sr. member
Activity: 364
Merit: 264
If people want to provide their addresses, I want to test transactions by sending them some TEST (lol). Until my bitcoins run out from all the fees ... lol.

BTC/XCP tips appreciated.
legendary
Activity: 876
Merit: 1000
Etherscan.io

Try the most recent update that phantom pushed.

So far, I've tried orders (both XCP > BTC and BTC > XCP) and issuance and they both seem to work.

Thanks. Just noticed that too.. and it looks like the orders are indeed working
sr. member
Activity: 364
Merit: 264
The transaction seemed to go through, but I am stuck with Status: 0/unconfirmed without any broadcasts for about 20 minutes so far. Bitcoin-qt is well connected (10 active connections). How long does it take typically?
It did actually go through, though not for 30 minutes.


Also, more error reports:

1. rpc-user and rpc-password should be prefixed with "bitcoind-" in the autogenerated config from the installer. Or at least make that part of it clear.
2. I still get the u2026 unicode errors in windows when doing "counterpartyd market".

Open Orders
Traceback (most recent call last):
  File "counterpartyd.py", line 608, in
    market(args.give_asset, args.get_asset)
  File "counterpartyd.py", line 41, in market
    print(str(table.get_string(sortby='Price')))
  File "c:\Python33\lib\encodings\cp437.py", line 19, in encode
    return codecs.charmap_encode(input,self.errors,encoding_map)[0]
UnicodeEncodeError: 'charmap' codec can't encode character '\u2026' in position
483: character maps to

This worked before (albeit being blank), so obviously some of the new transactions that have come up in the last day are causing this error.

Yes, running into the same issues. Even the order are not working and throwing errors. However I suspect this is only for the Windows builds because if you observe the transactions log there are buy/sell orders being placed



Here is another one for "order"

  File "C:\counterpartyd_build\dist\counterpartyd\lib\bitcoin.py", line 170, in serialise
    from pycoin.ecdsa import generator_secp256k1, public_pair_for_secret_exponent
ImportError: No module named 'pycoin'


Try the most recent update that phantom pushed.

So far, I've tried orders (both XCP > BTC and BTC > XCP) and issuance and they both seem to work.
legendary
Activity: 876
Merit: 1000
Etherscan.io
The transaction seemed to go through, but I am stuck with Status: 0/unconfirmed without any broadcasts for about 20 minutes so far. Bitcoin-qt is well connected (10 active connections). How long does it take typically?
It did actually go through, though not for 30 minutes.


Also, more error reports:

1. rpc-user and rpc-password should be prefixed with "bitcoind-" in the autogenerated config from the installer. Or at least make that part of it clear.
2. I still get the u2026 unicode errors in windows when doing "counterpartyd market".

Open Orders
Traceback (most recent call last):
  File "counterpartyd.py", line 608, in
    market(args.give_asset, args.get_asset)
  File "counterpartyd.py", line 41, in market
    print(str(table.get_string(sortby='Price')))
  File "c:\Python33\lib\encodings\cp437.py", line 19, in encode
    return codecs.charmap_encode(input,self.errors,encoding_map)[0]
UnicodeEncodeError: 'charmap' codec can't encode character '\u2026' in position
483: character maps to

This worked before (albeit being blank), so obviously some of the new transactions that have come up in the last day are causing this error.

Yes, running into the same issues. Even the order are not working and throwing errors. However I suspect this is only for the Windows builds because if you observe the transactions log there are buy/sell orders being placed



Here is another one for "order"

  File "C:\counterpartyd_build\dist\counterpartyd\lib\bitcoin.py", line 170, in serialise
    from pycoin.ecdsa import generator_secp256k1, public_pair_for_secret_exponent
ImportError: No module named 'pycoin'
hero member
Activity: 756
Merit: 502
Its 1 BTC per address meaning  1 person can "burn" as many BTC as he wants - it would just take him more time.

Yep, this what I meant.

Btw, congrats to devs for 700 BTC invested (burnt) XCP seems on it's way to 1K.

(If someone would say me a month ago people will willingly throw away 1M$+, I would say he needs to get his head checked! Smiley ).
Jump to: