Official Counterparty Dev Chat

Official Counterparty Dev Chat

Public archive of Telegram messages.

  • 2025

    • Sep 2025 (89)
    • Aug 2025 (20)
    • Jul 2025 (39)
    • Jun 2025 (65)
    • May 2025 (187)
    • Apr 2025 (44)
    • Mar 2025 (567)
    • Feb 2025 (44)
    • Jan 2025 (33)
  • 2024

    • Dec 2024 (947)
    • Nov 2024 (189)
    • Oct 2024 (1045)
    • Sep 2024 (112)
    • Aug 2024 (69)
    • Jul 2024 (257)
    • Jun 2024 (25)
    • May 2024 (340)
    • Apr 2024 (439)
    • Mar 2024 (128)
    • Feb 2024 (393)
    • Jan 2024 (2274)
  • 2023

    • Dec 2023 (397)
    • Nov 2023 (466)
    • Oct 2023 (173)
    • Sep 2023 (118)
    • Aug 2023 (158)
    • Jul 2023 (55)
    • Jun 2023 (1081)
    • May 2023 (2154)
    • Apr 2023 (594)
    • Mar 2023 (401)
    • Feb 2023 (270)
    • Jan 2023 (139)
  • 2022

    • Dec 2022 (115)
    • Nov 2022 (459)
    • Oct 2022 (479)
    • Sep 2022 (361)
    • Aug 2022 (518)
    • Jul 2022 (254)
    • Jun 2022 (67)
    • May 2022 (77)
    • Apr 2022 (349)
    • Mar 2022 (107)
    • Feb 2022 (71)
  • 01 June 2025 (11 messages)
  • @parodycards #16528 03:42 PM, 01 Jun 2025
    has anyone here tried using the public api for counterparty?
  • @XCERXCP ↶ Reply to #16528 #16529 03:51 PM, 01 Jun 2025
    Yes it’s good
  • @parodycards #16530 03:59 PM, 01 Jun 2025
    wild. i could not get my server to communicate with it. are you using dedicated hosting?
  • @parodycards #16531 04:02 PM, 01 Jun 2025
    are you successfully pulling info with javascript, php or something else?
  • @XCERXCP ↶ Reply to #16531 #16532 04:18 PM, 01 Jun 2025
    https://docs.counterparty.io/docs/advanced/api-v2/node-api/
    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.

  • @XCERXCP #16533 04:18 PM, 01 Jun 2025
    This
  • @XCERXCP ↶ Reply to #16530 #16534 04:19 PM, 01 Jun 2025
    https://counterpartycore.docs.apiary.io/#/reference/transactions/get-transaction-by-hash/get-transaction-by-hash/200?mc=reference%2Ftransactions%2Fget-transaction-by-hash%2Fget-transaction-by-hash%2F200
    Counterparty Core API · Apiary

    A place where APIs are kept.

  • @XCERXCP #16535 04:19 PM, 01 Jun 2025
    Is this what you are using?
  • @parodycards #16536 06:33 PM, 01 Jun 2025
    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
  • @codythecampbell #16538 07:10 PM, 01 Jun 2025
    Fuuun
  • @XCERXCP ↶ Reply to #16536 #16541 07:16 PM, 01 Jun 2025
    Request in https:
  • 02 June 2025 (3 messages)
  • @BuddybradleyBTC #16542 01:04 AM, 02 Jun 2025
    Joined.
  • @robotlovecoffee ↶ Reply to #16541 #16543 11:33 AM, 02 Jun 2025
    You can also use postman to test calls. It can be helpful to understand data and calls
  • @robotlovecoffee #16544 12:06 PM, 02 Jun 2025
    https://www.postman.com/ Postman: The World's Leading API Platform | Sign Up for Free
    Postman: 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)
  • @jp_janssen #16547 04:57 AM, 04 Jun 2025
    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.
  • @jp_janssen #16548 04:57 AM, 04 Jun 2025

    photo_2025-06-04_04-57-16.jpg
  • @codythecampbell ↶ Reply to #16547 #16549 07:17 AM, 04 Jun 2025
    Woow so what the heck ?!

    V11 or die kinda deal ?
    Spooky msg

    photo_2025-06-04_07-17-14.jpg
  • @jp_janssen #16550 08:38 AM, 04 Jun 2025
    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 😁
  • @papeto ↶ Reply to #16549 #16551 08:38 AM, 04 Jun 2025

    photo_2025-06-04_08-38-58.jpg
  • @codythecampbell #16552 12:23 PM, 04 Jun 2025
    Everything is fine odd and strange but fine
  • 05 June 2025 (1 messages)
  • @LongbranchBear #16553 12:20 AM, 05 Jun 2025
    Joined.
  • 06 June 2025 (31 messages)
  • @Saddam_H_Hussein #16554 12:40 AM, 06 Jun 2025
    oh ho tokenscan is in error.. needs to run the certbot .. ssh cert expired atm
  • @Saddam_H_Hussein #16555 01:01 AM, 06 Jun 2025
    ouch
  • @7740427332 #16556 01:14 AM, 06 Jun 2025
    Joined.
  • @jp_janssen #16558 10:27 AM, 06 Jun 2025
    Is Issuance with simultaneous Ordinal Inscription discussed/described somewhere?

    I am confused. How does it really work..?
  • @NorthrnSatosh ↶ Reply to #16558 #16559 10:30 AM, 06 Jun 2025
    https://github.com/CounterpartyXCP/counterparty-core/issues/3054
    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...

  • @jp_janssen #16560 12:24 PM, 06 Jun 2025
    This is taproot encoding.

    Ordinal Inscription is something else. (?)
  • @ffmad ↶ Reply to #16560 #16561 12:31 PM, 06 Jun 2025
    inscriptions are taproot envelopes
  • @herpenstein ↶ Reply to #16560 #16562 12:40 PM, 06 Jun 2025
    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
  • @herpenstein #16563 12:42 PM, 06 Jun 2025
    Taproot encoding of an issuance, fairminter or broadcast encodes the data in the description field is as an ordinal
  • @herpenstein #16564 12:43 PM, 06 Jun 2025
    https://github.com/CounterpartyXCP/counterparty-core/pull/3133
    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...

  • @herpenstein #16565 12:49 PM, 06 Jun 2025
    https://docs.counterparty.io/docs/advanced/specifications/taproot-envelope/
    Taproot Envelope | Counterparty

    The new taproot encoding allows embedding Counterparty data in transaction witnesses. It uses an envelope script similar to Ordinals.

  • @jp_janssen #16566 12:53 PM, 06 Jun 2025
    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?)
  • @ffmad ↶ Reply to #16565 #16567 01:03 PM, 06 Jun 2025
    Oh cool, it has already been added to the doc!
  • @ffmad ↶ Reply to #16566 #16568 01:07 PM, 06 Jun 2025
    I haven't researched it exactly but I don't think you create an ordinal token here
  • @ffmad #16569 01:08 PM, 06 Jun 2025
    You just use the inscription storage format
  • @jp_janssen #16570 01:19 PM, 06 Jun 2025
    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?
  • @ABlue0ne ↶ Reply to #16562 #16572 02:10 PM, 06 Jun 2025
    Coming in hot with that fire knowledge
  • @XJA77 ↶ Reply to #16566 #16573 03:09 PM, 06 Jun 2025
    Mmmm looks likes yes the ordinal is created by default if taproot encoding is active and the operation is issuance
  • @XJA77 #16574 03:10 PM, 06 Jun 2025
    And I believe the ordinal can be detached from the sat as you can reuse that sat inscribing on it other inscription
  • @XJA77 #16575 03:11 PM, 06 Jun 2025
    Not sure how to do it but I think is possible
  • @XJA77 #16576 03:11 PM, 06 Jun 2025
    I think with the same tools that allows you to inscribe in a rare sat
  • @herpenstein #16577 03:40 PM, 06 Jun 2025
    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
  • @jp_janssen #16579 03:53 PM, 06 Jun 2025
    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 )
  • @herpenstein #16580 04:01 PM, 06 Jun 2025
    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
  • @herpenstein #16581 04:03 PM, 06 Jun 2025
    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
  • @jp_janssen #16583 04:36 PM, 06 Jun 2025
    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
  • @jp_janssen #16584 05:02 PM, 06 Jun 2025
    One thing still unclear to me..

    ..the utxo containing the ordinal, can it be detached (conververted to a regular counterparty token) ?
  • @XCERXCP ↶ Reply to #16584 #16585 05:08 PM, 06 Jun 2025
    I thought the ordinal was just a bonus

    If you issue 100 quantity, you get 100 CP tokens + ordinal
  • @herpenstein ↶ Reply to #16585 #16586 06:43 PM, 06 Jun 2025
    Yeah I think you’re right. it’s just a normal ordinal and cannot be converted to a counterparty token.
  • @herpenstein #16587 06:50 PM, 06 Jun 2025
    Kinda like merged mining, but it’s merged minting. Your just using the same transaction to create assets on both protocols
  • @XCERXCP #16588 06:55 PM, 06 Jun 2025
    Great term, like it
  • 09 June 2025 (1 messages)
  • @gladystravis #16590 10:47 AM, 09 Jun 2025
    Joined.
  • 10 June 2025 (1 messages)
  • @8015097169 #16591 06:22 PM, 10 Jun 2025
    Joined.
  • 18 June 2025 (6 messages)
  • @NorthrnSatosh #16594 02:01 AM, 18 Jun 2025
    @codythecampbell xcp.io is a nice explorer that views total counterparty holders
  • @NorthrnSatosh #16595 02:02 AM, 18 Jun 2025

    photo_2025-06-18_02-02-31.jpg
  • @NorthrnSatosh #16596 02:03 AM, 18 Jun 2025

    photo_2025-06-18_02-03-27.jpg
  • @NorthrnSatosh #16597 02:06 AM, 18 Jun 2025
    721 355 results
  • @essnullvier #16598 12:03 PM, 18 Jun 2025
    Joined.
  • @essnullvier #16599 12:07 PM, 18 Jun 2025
    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)
  • @Arwyn_Official #16601 06:08 PM, 20 Jun 2025
    Joined.
  • 27 June 2025 (3 messages)
  • @7910233056 #16602 12:23 PM, 27 Jun 2025
    Joined.
  • @7910233056 #16603 12:24 PM, 27 Jun 2025
    Hello anyone have raw TX skeleton to spend m-of-n TX of old xcp ouputs to recover sats locked in them
  • @7994796529 #16604 01:17 PM, 27 Jun 2025
    Joined.
  • 30 June 2025 (1 messages)
  • @6517313784 #16607 12:42 AM, 30 Jun 2025
    https://odysee.com/@therealmartial-law:2
    @therealmartial-law

    houston burrus sui juris at law Tamerican Aboriginal title UCc1 jurisdiction common law natural law

  • 01 Jun 2025 (11)
  • 02 Jun 2025 (3)
  • 04 Jun 2025 (6)
  • 05 Jun 2025 (1)
  • 06 Jun 2025 (31)
  • 09 Jun 2025 (1)
  • 10 Jun 2025 (1)
  • 18 Jun 2025 (6)
  • 20 Jun 2025 (1)
  • 27 Jun 2025 (3)
  • 30 Jun 2025 (1)