- 15 May 2025 (225 messages)
-
You need to ask horizon -
you can just do things -
yeah -
thats the issue
-
asking on bitcoin
-
is not my thing
-
are you asking for some special marker?
-
i am not here to ask
-
i own keys
-
there are no special markers on bitcoin
-
i make decisions with my collection
-
i am looking explorer to show what i as a key owner request to show.
-
is it special?
-
so you want permissionless unique identifiers
-
this will stop people building on counterparty
-
you are centralising it on to few older projects
-
why should someone mint tokens with XCP?
-
why shouldn’t they?
-
trying to figure out your view of use case
-
Because sooner or later they will run in to permission to do something with their tokens
-
trying to play smart?
-
this is like asking why should people use staffed lines when there is self checkout
-
because they choose to
-
dude there is no use case of it
-
if it is not permissionless to act with those tokens
-
i issue token. and then i go ask Adam if he can do something for me?
-
:D
-
serious?
-
promote?
-
you see being collection as promotion ?
-
okay
-
now i got it
-
explorer instead of showing data
-
show only the data people paid for to be shown
-
worst of worse.
-
or just show the actual blockchain data alone
-
not showing or asking any permission
-
doxing
-
showing
-
asking
-
is all big bullshit
-
i want the explorer to serve my bio on all my creations
-
that’s not explorer job
-
ok whatever
-
asking someone is centralisation
-
you are not better.
-
make your own explorer that tells people the weather when a block was hashed if you want extras
-
stop accusing others of trying to centralize CP if you arent better
-
make disappear
-
is that a command line thing?
-
i promoted your website more than any collection was promoted on your tab
-
sad reality lol
-
you drink what you spit.
-
But it is okay, i believe in good work. and good work will be organically accepted.
-
Horizon Explorer has already been updated to the v11.0.0 beta, so previously invalid addresses are now un-mangled and valid. That's the only change. This fix is also required for real CEX support. -
how do the mangled addresses exist in the first place? -
is it because a checksum is added to a shortened public key hash?
-
Bech32 addresses were just truncated, then a fake checksum was added to force them to *seem* valid even though they aren't
-
but this wouldnt affect all bech32 addresses
-
only someone trying to send to a bech32m or something
-
Nope, just long ones
-
just trying to figure out how they made it into the db in the first place
-
lol it's a good question. It probably had something to do with there being literally zero tests for the codebase
-
This has details: https://github.com/CounterpartyXCP/counterparty-core/issues/3053Protocol Change Proposal: Fix Bech32 Address Support · Issue #3053 · CounterpartyXCP/counterparty-core
Fix Bech32 Address Support Motivation It has been 8 years since Bech32 addresses were introduced and became the standard for most wallets. Bech32 address support was added to Counterparty in 2018 w...
-
maybe @jp_janssen can shine some light
-
"Even worse, what if someone camouflaged a real P2WPKH address as a (fake) P2WSH address at some point?"
-
what a single advantage you have against anyone in this room against someone else on to any bitcoin explorer?
anything you can do more than others? -
seems look an odd thing to do because how could you ever sign from the fake address?
-
the point was equality. and if someone got on to the collections, others could have same equality to get there too.
-
so if i understand correctly the only addresses that would change would be invalid addresses and they'd just change to different invalid addresses?
-
Only invalid addresses change and they become *valid*
-
Data was just being deleted from the Counterparty db effectively 🤷♀️
-
Yup
-
very confusing how they were even recognized as valid txs in the first place
-
only think i can tell is a missing check in ownership transfer
-
They were forced to appear valid with the fake checksum
-
because that action requires a dust output
-
so if i did an ownership transfer right now to a bech32m it would produce a mangled address?
-
The point is that this was an error deep in the bowels of the Counterparty node code. Which is why we haven't fixed it till now...
-
Anything over 20 bytes
-
got it, and because its getting the address from the output itself and not message data
-
not actually "changing" addresses at all, but showing the correct one vs a mangled one
-
Bingo
-
got it, once i remembered ownership transfer used the dust output it became clear what happened
-
I would never advocate changing balances ofc 🙄
-
i mean you cant spend from a mangled address anyway, so nothing would have moved once going there
-
"In v10 and earlier a send to P2WSH would debit the P2WPKH. These tokens could have be traded with others and spread around the ecosystem by now, In contrast, on v11 the tokens would get debited to the P2WSH address and all txs directly and indirectly from P2WPKH will be invalid."
-
jp seems to think you can send from them? im confused what he's saying here
-
a send to a P2WSH goes to mangled address that cant spend, how are there now future transactions with those tokens from the address that cant spend?
-
This is what you can do with Fairmints too. Going to push some updates next week -
its the checksum that's different
-
because it uses only the first 20 bytes of the hash
-
so thats why the addresses match right up til the checksum
-
you could certainly recreate the mangled addresses if you wanted to, just use the first 20 bytes to get the checksum, slap it on the end and viola
-
If I'm not mistaken this is completely impossible. The mangled addresses were forced to *look* like P2WPKH, but they're unusable
-
yes this is my understanding also
-
maybe jp can give an example
-
very high for me :)
-
The mangled addresses were forced to *look* like P2WPKH, but they're unusable
Lmao wut?
The addresses were faked to look useable -
That’s incredible
-
Incredible we have Adam and the dev team digging so deep to fix literally everything
-
🙏 ty
-
Where would i access that? -
where would i find it...plz n thank you....
-
-
from this pov...web version...
-
thanks gonna give it a shot now
-
appreciate yall, lol CP gonna take the world by storm
-
The fix can't just be activated at a future block... obviously we'd have done that if we knew of a way to do it practically. It's not going to impact anyone's ownership of anything. Some addressed have been stored in the DB in a mangled form (so that they're unusable) and we're unmangling them.
-
it was mentioned earlier... But I think discussion of a protocol level way to categorize collections is an interesting proposition
For many years many people want the "green banner" and nowadays you can submit collections to block explorers like horizon.
Even on Casey's recent interview with Dan Anderson ... Casey asks when hearing about Rare Pepe "are collections a 'Counterparty' thing?" And Dan responds no... "It's just a website, WordPress blog" ....
Are there cons to having decentralized freedom to create "groups","collections", or categories any user could organize?
I just over the years see this discussion come up again and again. Anyway to streamline the process and have it be easier for new users creating projects with XCP assets? and not necessarily have to rely on block explorers to do so? -
I think like Mysterious mentioned, subassets is the way
-
One party has control over the subassets
-
What’s wrong with that solution?
- 16 May 2025 (33 messages)
-
The solution is restricted. Not all collections should be required to use the sub asset feature. Projects like NPCs and many others have used subassets in a great way but it shouldn't be required.
I'm just looking at other token chains and UI, and the ease at which creating a collection and the ease at which marketplaces and explorers can add them seems more streamlined than xcp collections
we have people either using the curated emblem collections or manually importing json lists and categorizing like fire mints, apps like Token dot art etc ..
why not community curate the "historic" collections or the main ones we all know and love, then let free reign to trustlessly and freely create lists or categories similar to opensea / ME UI data etc to minimize friction in collection creation for users, devs etc?
Though in xcp's case it could be tied in a similar way Token Asset Ownership is .. I see how subassets do this (and now they're free)... But that solution doesn't include collections like Kaleidoscope or Modern Relics where assets in the collection are made up of older ones... that most likely are not subassets
The process in theory of adding some sort of protocol flag (or some solution) could even be streamlined from the source of creation by adding some sort of flag during creation like if I was submitting to fake commons, and even before it's accepted I am required to add that categorical flag and once done I could look up the "in queue" commons submission with that protocol flag and see my submission and others
Just riffin! but I feel like some sort of solution would lessen the burden on all xcp explorers, minimize the fighting for collections and paid banners etc, and invite new features and users to a more structured, streamlined and efficient way to categorize assets and submit to collections
plus we could send whatever collection ownerships there are to 1BurnPepexxxxxxxxxxxxxxxxxxxAK33R -
It’s the same issue as “how do we attach an image to a token” and now we have like 10 different ways because everyone wants to do their own thing
-
All magiceden does is ask you to submit a json
-
At least that’s how they did it when i added bitcoin bricks
-
Maybe using a broadcast like COLLECTION|NAME|arweave_link_to_standard_json -
-
What's great about a json file is that it can grow over time as new series are added. If its hosted on arweave its kinda set in stone, right?
-
Horizon Market is doing the same, albeit its a bit of a manual process at the moment. I understand it will eventually be more of a turnkey solution, which I think is the missing link and why so many different standards have proliferated. Once there is an easy turnkey solution, where you don't have to author the json yourself, I think it could become the accepted "standard"
-
Another particular challenge: how do you determine who is the Collection maintainer with the authority to set the collection through a broadcast? A lot of collections are community/collaborative with many different artists.
-
hmm I see - ignore me then
-
just wondered if there was some sort of solution that could be devised to streamline the json data easily or categorize it at creation... Similar to memos when submitting to collections
some sort of standard for auto creation of collections or groups of assets -
Horizon Token Standard v1 · CounterpartyXCP/Forum · Discussion #142
The following is a standard for encoding Counterparty token data and metadata either entirely on-chain, or with the file data hosted with IPFS. With the upcoming Taproot‑envelope support (see Count...
-
Again, it just takes adoption and I think that's facilitated through tooling. If you make it easy for users and show them a singular method, it will get adopted.
-
As it stands, anyone can send me a collection JSON and I will get it to the Horizon devs so that it appears here: https://horizon.market/explorer/discover
-
Mmmm but this looks like reinventing the cip 25 that is already using many tokens
-
Will the CP envelope be an inscription ?
-
"CIP25" was low effort and broken at publication.
I've been working on a JSON standard since before that nonsense
It solves multiple problems, like facilitating collections, declaration of token type, and reputation building
I have not finished working examples, or a complete write-up, but I have created a master document to help prevent collision
https://xcpsite.com/test/schema.json
Feedback, Comments and questions requested @JSONstandard -
anyone building a wallet or explorer needs to account for every method used up to this point, schema fatigue
-
-
Or just ignore difficult things.
-
Kudos
-
Some users simply react without reading for comprehension
-
On-chain Stamp Collection Storage in JSON Format · Issue #450 · stampchain-io/BTCStampsExplorerOn-chain Stamp Collection Storage in JSON Format Overview Enable users to store their stamp collections as compressed JSON metadata on-chain, with support for large collections through chunking. Cu...
-
Imgur/Freeport standard worked out well for everyone
-
Unless I misread the room the topic seemed to be how to enable curators. I addressed the fact that this standard aims to solve a problem like that among others. And then I invited others to participate in working on this pre-release structure. It's unfortunate that some people want to become tropes but this message is not for the trigger happy. this is for those who understand that there are greater possibilities here than trading digital deeds. 🙇♂
-
i have a feeling it wasn’t targeted and just conceptual in statement
-
These phrases are indirect jabs masked as polite clarification, which is classic passive-aggressive tone.
-
This is what AI thinks, not me 😂
-
Banned!
-
There is no current open access standard for creating a collection
I'm offering to share the work I've done to remedy this
Please, name a JSON standard you were invited to participate in before release
/End
I'm not going to respond further here. Thanks -
Joined. - 17 May 2025 (7 messages)
-
Which AI are you using?🧐 -
-
I use them all but my go to is OpenAI
-
4127b4f40075db2fb92cb5b87937cef4a8505ca7015205926db39da9d5a3d59b
-
AND each asset in the collection also links back to the collection token THEWOJAKWAY
-
someone did create an asset to represent a collection at 2022-08-31 23:14:43 GMT
- 18 May 2025 (8 messages)
-
same, OpenAI has a head start in a lot but other are catching up. It also depends on what you are doing and your prompts -
i was asking chatgpt about JSON standards in the cryptoart space and it hallucinated a standard format for Rare Pepe. When i called it out, it gave me a correct answer
AIs lie and they tell you what you want they think you want to read -
that research paper about where that leads scared the ever loving shit out of me
-
I do not think that AI models lie per sa, they just are not this super power that is always correct. But they speak as if they are correct and most humans think computers are smart and do not check their work. It all comes down to context.
-
Not sure what you are refering to but there are futures that are not great, well for us humans 🙂
-
So hype for mobile minting
-
AI 2027
A research-backed AI scenario forecast.
-
Joined. - 19 May 2025 (18 messages)
-
Damned if we do, damned if we don’t
-
Can’t stop because our adversaries won’t, but I don’t think it will end well IMO
-
basically that is the TL;DR right there
-
-
Amazing they “knew” 40 years ago when they made Terminator
-
Published in 1986:
https://www.amazon.com/Arthur-C-Clarkes-July-2019/dp/0025258001 -
he predicted almost everything correctly
-
He really nailed the explosion of transgenderism
-
I’m also open to the possibility that the intelligence we perceive in AI is an illusion:
https://youtu.be/E31KuUJmqCU?si=Zsc9r6nAxR_LaX1OAI is a Nothingburger. You're wrong.My website: https://lukesmith.xyz Classical books reprinted by me: https://lindypress.net BTC: bc1qd20r7phdct3t0e0z6jqs55ulectg25pngt7hyl XMR: 89yML3AtqnTNdo3wNuoaW44D94Zx1kBZNSBc9SyNxGdaKEZwZNdVzvy9zpbzJMzysiWZEU3b5LwjQ3XwWuQsknCF8JK73yv Get a VPS and host a website or server for anything else: https://www.vultr.com/?ref=8384069-6G
-
Same could be said about humans
Everything we learn and invent is built upon previous context
AI is not even 3 years old yet -
You may want to ask the AI how old it is. I believe the groundwork started long ago
-
Apologies — he went overboard with the video title.
I don't have the skill set to have a strong opinion either way on AI.
Even the current generation of free AI tools is absolutely amazing. I have been using it rather frequently. But is it actually intelligent or conscious now? Will it be in the future?
It might just be an insanely powerful tool for extracting, organizing, and displaying, in human language, information from the world's largest databases.
I just shared the link above to provide an alternative view, given the high degree of excitement about AI, and all of the Pdoom discussions.
Regardless, it feels like possibly the most important developing technology at the moment, and I want to learn more and keep up to date. -
I recall in the 80's I had a dormmate in the sciences who was studying AI.
-
Alternative (more optimistic) scenario
https://ai-2027.com/slowdownAI 2027A research-backed AI scenario forecast.
-
Does anyone know what happened
-
-
0.0063 XCP per American
- 20 May 2025 (70 messages)
-
orangesurf (@OrangeSurfBTC) on X
Surprising facts from my new report on Bitcoin's UTXO set: - 49% of UTXOs are sub 1000 sats - 30% of UTXOs are inscriptions related - 100k+ 10-year-old counterparty UTXOs store arbitrary data with fake multisig pub keys Read it in full here: https://t.co/9TeTj8ZIqB
-
So i tired to buy from a dispenser and got nothing. -
-
Tried to buy from 3 different dispensers and got no xcp
-
https://live.blockcypher.com/btc/address/bc1q3r3cme8qnjcqa7835k0ylenpqc4utl6acsvxa6/
https://blockstream.info/tx/16d536cfb6424458fd9770b8ce3d1992b8759342c775070ec10e00b2a8be51a2
https://blockstream.info/tx/60ff55f6b191ee097a5817bbfce327020f55f6ceca337c3b44dec1d6a7481739 -
Where'd the xcp go? What did I do wrong?
-
Did you buy dispensers on freewallet Mobile?
-
No not my wallet
-
No i used another wallet to buy dispensers
-
Casa wallet
-
Sent from casa to btc address
-
That's where the screenshot is from yes but I used casa wallet to send the btc to dispenser
-
Casa didn't update?
-
So I've had a first look into this, and it looks like these are the dispensers you bought from, 22 hours ago
-
One of these is my dispenser. If you tell me which addy is a counterparty addy I will send you the XCP -
Looks like 13wuG1KQTrv2GQLsxkdNJZSreD5TRck8Wa is your wallet with XCP in it. This is the addy you paid me from. I will send to this addy.
-
I will have to close the dispenser which takes 5 confirmations. Might be tomorrow (in 9 hours) before I can send.
-
Yes pls. And thank you so much
-
@krostue could you send me the xcp I purchased
-
And you can only buy whole amounts of XCP from most dispenser. The amount you sent was for 119.83 XCP which would only give you 119 if it was dispensed.
-
-
-
👀👀
-
Only displays like this on unconfirmed in tokenscan
-
Ya that's fine. I m not good at math
-
I think i bought some xcp from your dispenser... I didn't get the coins but you got my btc
-
💴⛏️ AFK
will remedy tonight -
Sorry I didn't look close enough, as to notice one of my dispensers was involved.
I like to use mempool.space and didn't feel like pasting your all your transactions individually to inspect them at the time -
huh! the wallet without a warning on the xcp website puts users at risk for not updating with dispenser change (about a year ago?)
-
-
BS comment, sometimes things are missed
-
Casa tookan is also an Everdream Soft app
-
It’s almost like you have to trust individual wallet devs and not a static website
-
Looking at the Horizon wallet, does it inspire confidence? Do the wallet devs inspire confidence? Does the user experience inspire confidence? -
Trustworthy people are perfectly capable of making bad decisions about dependencies, update procedures, privacy, testing, making unusable UIs and of course security! Maybe audits inspire confidence.
-
Sure I just mean trust as in, you need to trust that they’re implementing changes etc
-
I don’t use horizon wallet so I don’t have an opinion on it
-
I will say rpw had dispense message implemented at activation block
-
I’ve used it and it’s great
-
im simply frustrated while this change was hypothetical I mentioned issues exactly like this would arise far into the future
there wasnt quick cohesion by the community for the upgrades to what was presented as a critical "bug" in the code (ninja took a few months and casa still isnt upgraded)
how much of that is wallet dev responsibility vs communications and pressure by protocol devs for user safety?
(side note, imagine fw mobile was upgraded lol) -
RPW is so very to use 🔥
-
How is this any different then sending to a dispenser that’s emptied prior
-
There was someone here two days ago that had to reach out to dispenser owner because of that
-
That’s why there is a list of trusted dispensers in the first place
-
Easy to point the finger
If you were so worried, why didn’t you test them all -
-
It is 100% the wallet devs responsibility to stay up to date with protocol changes
-
I say that as a wallet dev
-
It’s such a basic change too, really takes the minimum amount of effort to implement
-
But at the end of the day, you should never send bitcoin to an untrusted dispenser anyway, so is this really an issue?
-
I was vibe coding a wallet with my AI but I think it stole the money I put there
-
Sent it to its AI buddies
-
Casa Tookan doens't support the new dispenser strategy yet.
Due to scarce ressources it has been late. I will check how to put this in the pipeline asap -
Not a question I have a thought that say hypothetically is it possible that he created his own currency or token in other words on the counterparty site and put bitcoin in it or Ethereum in it that say and call it rusty or rustbits and then in order in order to get it off your Blockchain into something that is more liquid that say Ethereum or Coinbase, I would need to send a message or a memo with my delivery and or have a node or something like that in order to actually receive the eth that I hid under my rustbits. Oh, that stuff you know adding security to my decentralize self custody funds correct would that be possible? Could how would I investigate that? -
Im unable to parse what you are asking in this question
-
but a quick search shows you had one week to complete the swap almost 6 years ago, so you have a collectable without market value
https://bitcointalk.org/index.php?topic=1895425.msg52009642#msg52009642 -
"Not a question I have a thought that say hypothetically... "
"Could how would I investigate that?"
its very hard to understand what you are asking so I can only guess how to answer. - 21 May 2025 (82 messages)
-
I guess that’s means I missed out on my chance. Do you want to buy some rustbits? Hey, if it went to eth then why couldn’t I just use the same process as I did to get etherdelta and why would you only have a week?
-
But please don’t try to insult me I’m trying to figure this out and no it’s not a quick search to find what you found I probably read through every link on at least 2 separate instances.
-
And to my previous thought/ question is could I hide a token or coin under some fictitious thing like an nft, or personally created token and make it difficult for someone to steal it by making it only accessible with a memo/comment/message and/or node to protect my assets? maybe, that is a known fact or thing or maybe I think feloniously and want to make it extra hard for someone
-
No, this is not possible. I looked at the wallet you provided and it is basically worthless.
-
I do appreciate your humor and information I’m new to this and I feel as if I should know a lot more about these things to be talking to you guys typically my level of understanding of crypto person doesn’t come
Across your blockchain -
I’m not saying that this wallet is doing that. I’m just saying couldn’t you disguise an nft to hold tokens and coins yes, essentially like royalties or something, right? So yes I think I’m right
-
You know, I’m sure glad everyone knows who I am and y’all looked at my wallet and that I shared with you. I don’t know like two weeks ago and y’all know everything about my wallet and your positive that’s not what’s happening. I’m positive too, but I’m glad to know you’re still looking at my wallet.
-
years ago when the swap happened there were no tools and it was a manual process where a person controlling the situation received information and distributed new tokens elsewhere. this person isn’t active and they had a period to complete this task and it ended almost six years ago so no, you can’t go to ether delta and do something to make this happen.
you have some expired lotto tickets that cannot be claimed and only hold value in a historical sense. but it got you to study and learn so maybe that was the value all along -
Horizon imported wallets are broken and have been for some time. I am unable to find their room to make the report
-
could someone @linkme?
-
fw does not import segwit, and horizon is not working. so, i cant send your XCP. unless things work by tomorrow, ill just send a refund in btc
-
i reported it to you in PM and you brushed me off
-
you all even use the stuff you make? then maybe you can discover your own bugs
-
two different wallets and the same problem. yeah it must be me
-
Nah. Fix your broken stuff yourself.
I simply won't use it because of the attitudes involved -
Last time I tried giving Adam some sound advice I suggested he reexamine his pricing structure. Looking at the amount of traffic on horizon for the last 2 months it seems like he had every right to shut me down because it's so popular
-
Ok let me know what u end up doing
-
Ok pls let me know when you can send them....IF you gonna send btc can you send to this wallet address instead?
bc1qjrp6y7nkj0njf90z4jlnsqfherjp5n6jzh0dzz -
Any update on identifying the owners of 2 and 4?
-
Looking for the owner of wallet
1Ea7GFTA8cBNcpKNQsVnXgXB4RUFmkCWvM
I bought from your dispenser and never got my xcp! Please reach out
Heres the transaction:
https://blockstream.info/tx/60ff55f6b191ee097a5817bbfce327020f55f6ceca337c3b44dec1d6a7481739Blockstream Block ExplorerBlockstream Explorer is an open source block explorer providing detailed blockchain data across Bitcoin, Testnet, and Liquid. Supports Tor and tracking-free.
-
My hot take, take with a grain of salt since I have been uninvolved and just show up here with this:
The core dev team putting out a protocol without a reference implementation of a wallet version for every major release is a sign of poor process and quality control. Having a reference wallet implementation is a critical part of developing the protocol. No need to be pretty (and this one is not) but it should implement COMPLETE COVERAGE of the feature set.
For every Counterparty client function, demonstrate that it works and show wallet makers how it can be implemented. If you can't implement the features, how are you testing them? I mean if you can build a custom test harness, you can build a working wallet. Criticize freewallet all you want, but at least all features got implemented. Please prioritize wallet development to become a working deliverable with every new release. -
Also looking for the owner of wallet:
16TNY6JF5dkYC3ghRuJ9nb27oE9Z6zA3GM
I bought from your dispenser and never got my xcp! Please reach out
Heres the transaction link
https://blockstream.info/tx/db681cb0c1056be90d191260f17015cca8cecdd2369d72fa8c63c75fcf69362cBlockstream Block ExplorerBlockstream Explorer is an open source block explorer providing detailed blockchain data across Bitcoin, Testnet, and Liquid. Supports Tor and tracking-free.
-
all compose functions are easily accessible via the rest API
-
So the normie masses that are supposedly soon flooding in should interact with XCP via API? It was said that everything will become easier and streamlined to one click actions. -
Nope didn’t say that, just that a reference implementation exists
-
Personally I think rare pepe wallet is very easy to use even for normies
-
No, a aspect of a reference implemention is a fully functional program as demonstration.
-
The API is fully functional, you literally just need to sign the tx
-
The API is an Interface
-
I think a cli wallet would be nice, I believe it’s on the roadmap
-
But I’m not going to demand anyone build it
-
yep. and there's a pre-alpha around.
-
Does the v11 beta has the protocol change active?
-
Is it on GitHub?
-
yup but I won't link to it because it's unsafe to use
-
how confident are you in horizon wallet safety?
-
This channel is for discussion of Counterparty, not any particular wallet or explorer or whatever. Counterparty is a decentralized community and ecosystem, and development of the protocol is intentionally very heavily decoupled from development of any user-facing tooling. Obviously everyone would be happier in the short term if development was fully centralized and vertically integrated, but that's much worse in the long term. (This is why the whole ecosystem is in the state it's in today.)
-
Fully confident. Otherwise we wouldn't deploy it to production. And ofc I use it myself daily with no qualms.
-
Your confidence is based on what? I mean this wallet can't even sign a message. Is there an easier thing to implement in a wallet? I dare you to start a bug bounty. And dismissing the importance of a reference wallet is just insulting.
-
I suppose if nobody made a working wallet it would just be an academic problem?
-
token gated access
-
also "it's coming" isn't very satisfying
-
I see there is the sign message API on the horizon provider file, don't know how to trigger it as there is not docs but is one of the exposed function, and yes, is a really important feature
-
i’ve created assets that required signed messages to obtain, i’ve used it in OTC deals, i’ve used it because it’s an intrinsic feature of bitcoin. it’s not something to dismiss because you haven’t used it
-
What’s wrong with it’s coming?
-
I suppose it's better than "not gonna happen"
-
Joined. -
Horizon has created a wallet, an explorer, an extension, a market place and more is coming
CP core devs have literally updated the entire bones of the protocol so it doesn’t take a week of parsing to set up a node, created and documented an insane new API, added new features like atomic swaps and are still going
All of this has been done FREE while working their ass off doing it
Bugs will exist, that’s software, users need to use software to find every edge case
I don’t get how some can be so hostile to the people trying to help CP the most -
Criticism is not hate. It's not in anyone's best interest to discourage critics.
-
I think the critics wouldn’t exist if the prices were higher
-
You don't know me at all
-
I don’t even consider it criticism though, it’s a request, a bug, a question, etc…
-
I cannot be more aligned with this
-
But this is not 100% true
-
Close conversations, restrict people to contribute and silence different opinions is not decentralization
-
I understand that in a 100% decentralized development all this necessary updates would take years to accomplish, and I'm pretty sure that the protocol will be more decentralize progressively
-
The “that’s not decentralized” argument is the same in Bitcoin development too, everyone has a different opinion on what that actually means
-
And to be fair, it’s been a criticism since 2014
-
Joined. -
Anyone have a sense of what reusable code is already inscribed on-chain? I mean aside from 800 copies of p5.js. I'm thinking JS and CSS but could be any, thanks in advance.
-
Let me know if you find a good resource for this
-
There are some reusable code in stamps too, @herpenstein stamped a few code I think
-
We have q5js, w.js and bonsai.css on stamps as well -
We need to publish the locations but I can find all the trx hashes for them on the stamps db.
There is also https://github.com/jokie88/ordinalpublicgoods -
All the recursive fun
-
This is what I was looking for, thanks!
- 22 May 2025 (21 messages)
-
thanks! exactly what I was thinking of 🙏
-
Joined. -
Did you send the btc back yet? I don't see it
-
Let's keep the discussion of Horizon stuff to @HorizonXCP
-
User banned. Try pm
-
just detected balances discrepancies between versions 11.0.0-alpha.1 and 11.0.0-beta.1, opened a github issue with details here:
https://github.com/CounterpartyXCP/counterparty-core/issues/3165Balances discrepancies on API · Issue #3165 · CounterpartyXCP/counterparty-coreHello, im detecting some discrepancies in balance between version 11.0.0-beta.1 and the version 11.0.0-alpha.1 version you are running on testnet: YOURS: https://testnet4.counterparty.io:44000/v2/u...
-
I believe I already answered you on this issue... you were running an out-of-date version until very recently. We'll double-check, but if you don't upgrade before the activation dates, you're gonna have a bad time.
-
Always compare only the latest version of develop (which this is *not*) to the previously released version (v10.10.1)—otherwise you'll probably only find bugs we already fixed.
-
respectfully, i already told you that i was in the last released stable version when the reorg issue happened (10.10.1) the one we discussed in dm and that for me is a bit tricky to test again. this is another issue, i updated to the beta one (11.0.0.beta-1) to see if that solves the issue, and it doesnt i fully delete db and resynced to see if was my issue and is not so i believe there is a bug
-
what version should i be running on testnet to match the one you are testing (11.0.0-alpha.1) as i cannot find on github this release tag
-
the one in develop matches with 11.0.0-alpha.1?
-
anyway i dont understand why if there is not a protocol change activated yet between v10.10.1 and v11.0.0 (as you told me) to see discrepancies in balances unless in testnet it is activated for testing it) but as im not using a p2tr addresses i should not be seeing discrepancies...
-
im now resyncing in 10.10.1 to see if that solves it
-
looks like now after a full resync is detecting the assets but this does not makes any sense
-
there is a bug 100% sure with reorgs.
-
Please file a *detailed* bug report and don't compare anything with v11.0.0-alpha.1, obviously. Only compare with develop.
-
what is your instance and api of develop to compare with?
-
There isn't one. (You shouldn't need one.)
-
@memoryorbs shout out to Duncan for paying back my btc after using casa tooken
-
Brup!
- 23 May 2025 (4 messages)
-
Joined. -
None -
Agree 🤙
- 24 May 2025 (4 messages)
-
-
I’m really excited about inscriptions on CP. It’s a game changer. Even if we can only capture a few percent.
-
I don’t understand why anyone would ever issue just an ordinal again tbh
- 25 May 2025 (16 messages)
-
For anyone attending the Lisbon conference, Counterparty will have thorough representation.
https://www.nonfungibleconference.com/agenda-global -
-
-
are you going?
-
oh i see mike in space on there now lol
-
Yeah was a lot of fun last year. Lisbon is lovely. Planning to stay a full week this time.
-
So many -
Legendary, Mike or Shaban
Hard to discuss the history of NFTs without mentioning them both -
Same with the founders the CP
-
But CP does really have so many
-
Mike definitely a legendary artist .. I love trumprare card made by mike -
Wrong Mike 😁
-
Why? 😁😅
-
It’s a common name 🤷♂️
- 26 May 2025 (1 messages)
-
- 27 May 2025 (28 messages)
-
✨ Announcing Counterparty Core v11.0.0 ✨
This is a big release with multiple protocol upgrades and many improvements to the API, CLI, codebase, and test suite.
Protocol Upgrades
* Fix Bech32 address handling and finally add support for P2WSH and P2TR
* Support Taproot envelope data encoding, which will significantly reduce transaction fees for larger txs (and removal of support for P2SH data encoding, which is strictly worse than Taproot)
* Support simultaneous Ordinals Inscription creation when composing an Issuance, Fairminter or Broadcast txs (docs: https://github.com/CounterpartyXCP/Documentation/blob/f5647d7b8da7c578bb9d2cae892c2d697bf84796/docs/advanced/specifications/taproot-envelope.md)
* Allow soft_cap to be equal to hard_cap with Fairminters
* Add max_mint_per_address parameter to Fairminters
Note: This release is a protocol upgrade. All nodes must upgrade by block 902000 (in ~3 weeks).
Full release notes are on GitHub: https://github.com/CounterpartyXCP/counterparty-core/releases/tag/v11.0.0 -
None
-
Reviewing this chat, saw the comment, reminded me of an endorsed comment I made a month or so ago. Commenting off an RPT post. -
Holy shit 🔥
Does this go live in 3 weeks or is it live now? -
Approx 3 weeks. Block height 902 000
-
Damn! Ordinal issuance on fairminters and broadcast too!
-
This blows past what I was thinking
-
This might be the most insane update in the history of CP
-
This is cool!
-
Fairmints will be ready 👍
-
LFG, did CP just make ordinals fungible
-
Thanks for the extra week!
-
Joined. -
What do you mean?
-
That’s my initial thought, need to think about it more, but each ordinal issuance is associated with a CP asset from what I understand with faitminters
-
So no more worries about pruning or? Idk I am not that technical
-
Ok Casey
-
Huh
-
Not ordinals, STAMP -
Oh didnt get it for the new mecanism of v11.0, i m a bit lost to be honest with this upgrade.
-
Can someone explain me like i m 5, how is this affecting regular/old counterparty transaction or are they just for the atomic swap part of cp
-
Simple terms It will create a new asset class issuance on counterparty utilizing the witness data space
-
Okay thanks, so it will not affect the old issuance and transaction way for « regular » cp asset as i understand
-
-
-
Yep, already did :)
- 28 May 2025 (19 messages)
-
Basically they can’t become a real stamp anyway because they are prunable. Kind of against the ethos. Hence why stamps are a subset of counterparty. Leveraging the killer aspects of the CP token layer and ensuring immutability by the definition of becoming a stamp. Yet still sharing the token trading capabilities across ecosystems. Meta-meta-layer for real.
-
It’s great to have prunable tokens in cp, at least they aren’t ipfs hosted. And cheaper for those that can’t pay the premium to miners for an unprunable stamp. Not to mention the data storage size which is contrary to stamps compressionism, but damn well useful
-
Is something wrong or updating? Can't send anymore from rarepepewallet and all BTC balances in Freewallet showing 0. Everything was fine 20 minutes ago.
-
Should be fine. Had that happen a few times past weeks
-
Working fine again
-
The definition of insanity is doing the same thing over and over again and expecting different results
-
J Loone Brickens 🧱 (@wasthatawolf) on X
RARE PEPE TECHNOLOGY UPDATE! Rare Pepe Wallet has been updated to v0.7.0 with full support for UTXO-attached pepes and atomic swaps. What does this mean!? 🧵
-
Joined. -
If anyone has any technical questions on implementation pls ask!
-
Coming soon, for now I want people to get comfortable with the underlying tech
-
I have will dm you sir
-
There was a guy verifying dispensers in here, is he still around? -
Like where do you sell/buy xcp now?
- 29 May 2025 (70 messages)
-
Joined. -
Joined. -
If yall weren't in this industry id be ghosty
Love you Gs -
Not in practice.
Only being able to do one transaction at a time is quite a hindrance. Not to mention to cool feature of getting attachments combined by just doing a regular send.
Would not recommended testing with assets you care about -
There needs more unity not utility but unity
-
Unity has made CP basically have zero growth for the last 10 years
The one time CP did grow, aka stamps, it caused non unity 😂 -
The truth is, if you don’t have haters, you’re not doing anything
-
Thanks for the compliments
-
Duncan, I don’t hate you because you actually don’t do anything.
I hate you because you are the most miserable trolling person in the universe lmao -
Too bad you are unable to have intelligible conversations with people with differing opinions without resorting to character assassination
-
-
-
@jp_janssen raised an issue with the latest v11.0.0 release. (Boy did he communicate it badly.) We made a minor change to the transaction encoding scheme to like, _make it better_. But apparently bugs are features 🤷♀️ , and tbf there _wasn't_ any public discussion of this change, even though it _does_ effectively change the API in a non–backwards compatible way. If anyone has any opinions on the matter, there's now a GitHub issue for discussing it: https://github.com/CounterpartyXCP/counterparty-core/issues/3173
-
"Boy did he communicate badly"
I literally showed you the transactions and the exact bytes that were off. Explained why it made libraries non-backward compatible.
I made it perfectly clear but were attacked for reporting .. again. Im too tired of your manipulation. Bye!
PS. v11 is a minefield of bugs. I will not report bugs anymore. Do not upgrade, err downgrade 🙊 -
But you blocked him for commenting further?
-
What will older versions return on parsing with the new message filed?
Will it fail or skip or misread? -
Will the parser know there’s an issue on prior versions?
-
an older version can't parse the new encoding but this is always the case
-
Why would anyone ever go back and parse with an older version
Assets are going to be missing, etc… it makes no sense unless you are purposely forking -
Not fully, but partially?
-
it would see that its a counterparty message but wouldnt validate
-
So the version 11, if someone was running 10 to parse, they would know there’s an issue being returned by the software?
-
i dont know what you're asking here
-
its a consensus update, you have to run the new version
-
Yes, I’m not asking if the assets are all located in the same addresses, I’m asking if I run 10 and CP sees the new tx type, what will happen?
-
-
invalid
-
So they are aware
-
The parser using 10 is aware of an issue
-
No I just closed the issue because it was talking about different things. He was upset that like the message encoding changed at all, even though it changes regularly 🤷♀️
-
I open a new issue to discuss the actual matter (which he doesn't mention) which is the use of CBOR
-
If the txs are invalid on parsing with prior versions, I personally don’t understand the issue myself
-
Yeah ofc they are. The issue (which JP did raise!) is that client libraries have to change
-
That was unplanned, and is worthy of discussion
-
-
This 😆
-
I know. Super scary 👻
-
On top of it if I understand correctly, the only txs returned invalid will be the one using the new field, so it literally has zero change on assets issued prior
-
*of course*
-
you're overthinking it, the main thing that changes is anyone building txs in the client with their own libraries has to update their encoding
-
Yes, but not for the history buffs
-
So the entire argument is null in my view
Literally just expanding CPs capabilities -
On future abilities
-
The library change, ok
-
Yeah the issue is JP wrote a library for constructing txs client-side many years ago and now he'd have to change it (not a lot!) Which is like _normal software development_. But that kind of thing is very upsetting to some people. And the Counterparty community in general is extremely resistent to any change whatsoever, even (especially?) when it relates to minor technical implementation details.
-
Because they hear stupid stuff that’s not true and how their historical assets are done when it literally has zero affect on them
-
It's especially weird to see people so angry about me changing eg a tx encoding scheme that I designed in 2013 lol
-
GM -
yeah its not a huge deal, just a bit of a pain to update libraries, test in production etc
-
but its not a dealbreaker
-
Believe it or not I don't want to create pain for any wallet devs or users (pretty sure I am both myself)
-
i need to implement the taproot envelope into my library eventually anyway
-
light the fire lol
-
i think the toughest thing right now is an easy wasy to test and compare since the API doesnt update until activation block, would be nice to have like a data_postactivation field or something
-
You can run a dev node with --enable-all-protocol-changes (or something. I forget) to force-activate ahead of time
-
actually shouldnt i be able to look at test suite txs too?
Counterparty General Chat
Public archive of Telegram messages.
- 01 May 2025 (16)
- 02 May 2025 (68)
- 03 May 2025 (10)
- 04 May 2025 (90)
- 05 May 2025 (66)
- 06 May 2025 (20)
- 07 May 2025 (3)
- 08 May 2025 (18)
- 09 May 2025 (13)
- 10 May 2025 (17)
- 11 May 2025 (16)
- 12 May 2025 (28)
- 13 May 2025 (28)
- 14 May 2025 (11)
- 15 May 2025 (225)
- 16 May 2025 (33)
- 17 May 2025 (7)
- 18 May 2025 (8)
- 19 May 2025 (18)
- 20 May 2025 (70)
- 21 May 2025 (82)
- 22 May 2025 (21)
- 23 May 2025 (4)
- 24 May 2025 (4)
- 25 May 2025 (16)
- 26 May 2025 (1)
- 27 May 2025 (28)
- 28 May 2025 (19)
- 29 May 2025 (70)
- 30 May 2025 (11)
- 31 May 2025 (85)