- 01 June 2025 (11 messages)
-
has anyone here tried using the public api for counterparty?
-
Yes it’s good
-
wild. i could not get my server to communicate with it. are you using dedicated hosting?
-
are you successfully pulling info with javascript, php or something else?
-
API v2 | Counterparty
The Counterparty Core API is the recommended way to query the state of a Counterparty node. All other methods have no official support.
-
-
Counterparty Core API · Apiary
A place where APIs are kept.
-
-
I attempted to use the data from api.counterparty.io:4000/v2/ inside my webpage with no success. Since you have had success, maybe you can answer my questions so that i can narrow down the difficulty that only i must be having
-
Fuuun
-
Request in https:
- 02 June 2025 (3 messages)
-
Joined.
-
You can also use postman to test calls. It can be helpful to understand data and calls
-
https://www.postman.com/ Postman: The World's Leading API Platform | Sign Up for FreePostman: The World's Leading API Platform | Sign Up for Free
Accelerate API development with Postman's all-in-one platform. Streamline collaboration and simplify the API lifecycle for faster, better results. Learn more.
- 04 June 2025 (6 messages)
-
Counterparty v10 has a kill switch! All nodes will die at block 902,000.
I tested this by pointing config.py to a custom url indicating that activation already happened. -
-
Woow so what the heck ?!
V11 or die kinda deal ?
Spooky msg -
I try to dig into history here.
In 2018 checks.py did load a json, checked for version and killed the node if not updated.
So it appears not be some new conspiracy. Just an old one from the early days 😁 -
-
Everything is fine odd and strange but fine
- 05 June 2025 (1 messages)
-
Joined.
- 06 June 2025 (31 messages)
-
oh ho tokenscan is in error.. needs to run the certbot .. ssh cert expired atm
-
ouch
-
Joined.
-
Is Issuance with simultaneous Ordinal Inscription discussed/described somewhere?
I am confused. How does it really work..? -
Protocol Change Proposal: Taproot Envelope Data Encoding · Issue #3054 · CounterpartyXCP/counterparty-core
Taproot Envelope Data Encoding Motivation Since its inception, one of Counterparty's main technical challenges has been efficiently storing data in the Bitcoin blockchain. Currently, two method...
-
This is taproot encoding.
Ordinal Inscription is something else. (?) -
inscriptions are taproot envelopes
-
OP_FALSE
OP_IF
OP_PUSH "ord"
OP_PUSH 1
OP_PUSH {description_mimetype}
OP_PUSH 0
OP_PUSH {description}
OP_PUSH 5
OP_PUSH {other_issuance_data}
OP_ENDIF -
Taproot encoding of an issuance, fairminter or broadcast encodes the data in the description field is as an ordinal
-
Ordinals Compatibility by ouziel-slama · Pull Request #3133 · CounterpartyXCP/counterparty-core
Use CBOR encoding format for Sweep, Enhanced Send, Fairminter, Fairmint, Issuance and Broadcast Add mime_type in issuances, fairminters and broadcasts tables Add mime_type parameter for compose_iss...
-
Taproot Envelope | Counterparty
The new taproot encoding allows embedding Counterparty data in transaction witnesses. It uses an envelope script similar to Ordinals.
-
Thanks! Docs explained it. Ordinal is optional, but why is it default?
Does it mean you issue N counterparty tokens plus an ordinal? Can the ordinal be detached from the utxo (become a regular counterparty token?) -
Oh cool, it has already been added to the doc!
-
I haven't researched it exactly but I don't think you create an ordinal token here
-
-
Ok, super important to get this straight.
I'd hate to see N counterparty tokens + 1 ordinal issued by default. If that's not the case, fine then i can relax ☺️
Second, CBOR now has become optional right? You can still use old encoding? -
Coming in hot with that fire knowledge
-
Mmmm looks likes yes the ordinal is created by default if taproot encoding is active and the operation is issuance
-
-
-
-
I’m not 100% sure but I think it should work fine with any address type. The counterparty indexer creates and signs the reveal tx. So you use any address and use the api to create an issuance, the api creates a tx with an op return and an output large enough for payment to the reveal address generated by your data, and a signed reveal tx using your data and a random key that sends the destination address your ordinal. Then all you need to do is sign the first tx and broadcast it, then broadcast the second tx. Then you should probably send the ordinal to a different address. Fwiw, I keepy my different protocols on different addresses just for safety.
Also I haven’t been paying close attention lately as I have a lot of personal stuff going on, so I may not have the details perfect. Always double check anything a derp tells you -
Your replies are appreciated.
The pieces start to fall into place but i still don't quite understand it.
Taproot encoding is not necessarily ordinals.
By modifying cntrptry messages with CBOR encoding it becomes possible to taproot encoded counterparty messages compatible with ordinals.
Compatible issuances, broadcasts etc will show on ordinals explorers.
This is the default behaviour in v11 (for messages >80 bytes only?)
Is it also default that a tradeable utxo is assigned to the ordinal? ( sorry if i keep asking, incredibly important to get this detail right. Im writing up an opinion on v11 ) -
I think that default behavior for issuance is that the api will generate a tx that creates the desired number of counterparty assets (not bound to any utxo) and simultaneously a single ordinal. Then you will be credited with those counterparty assets at the destination address and a single utxo containing the ordinal. I also think the api has a Boolean flag for opting to store the data in taproot without the structure necessary to create an ordinal, in which case you would simply receive only counterparty assets at the destination
-
So if you chose to issue the ordinal (with the api flag) in the api call, you will get an ordinal and the asset will show up on ordinals explorers
-
Yea, the docs state this about taproot encoding:
A first format optimized for size and not compatible with Ordinals
A second format totally compatible with Ordinals inscriptions
The second format is automatically used with the following transactions:
Issuance
Fairminter
Broadcast -
One thing still unclear to me..
..the utxo containing the ordinal, can it be detached (conververted to a regular counterparty token) ? -
I thought the ordinal was just a bonus
If you issue 100 quantity, you get 100 CP tokens + ordinal -
Yeah I think you’re right. it’s just a normal ordinal and cannot be converted to a counterparty token.
-
Kinda like merged mining, but it’s merged minting. Your just using the same transaction to create assets on both protocols
-
- 09 June 2025 (1 messages)
-
Joined.
- 10 June 2025 (1 messages)
-
Joined.
- 18 June 2025 (6 messages)
-
@codythecampbell xcp.io is a nice explorer that views total counterparty holders
-
-
-
721 355 results
-
Joined.
-
Hi, we are looking to add to the team:
- Devs (Solidity/Rust/Move/Go/C++)
- Auditors & Protocols experts
- BD Managers
If you are interested - DM me - 20 June 2025 (1 messages)
-
Joined.
- 27 June 2025 (3 messages)
-
Joined.
-
Hello anyone have raw TX skeleton to spend m-of-n TX of old xcp ouputs to recover sats locked in them
-
Joined.
- 30 June 2025 (1 messages)
-
@therealmartial-law
houston burrus sui juris at law Tamerican Aboriginal title UCc1 jurisdiction common law natural law