- 18 March 2025 (537 messages)
-
-
oh yes boy i paid you
-
-
-
-
-
-
I also paid. Development was received and is on-going
-
-
-
-
Smells like a smear campaign before Xchain.
-
-
-
-
-
many donated, doesn't mean I work for them personally or am to implement their ideas... simply means that I was paid to work for the "COMMUNITY" and implement things the COMMUNITY came to consensus on... you never took the time to follow guidelines and write your ideas up as CIPs, not my fault... if you want your ideas taken seriously, gotta do more than just rant in a channel about how your genius and everyone elses is dumb.... your smart, you know this, but you refuse to ever conceed that anything is your fault, including inability to present your ideas in a clear concise way... you prefer ramble text-walls.
-
YES IT MEAN
-
-
-
nope, want to get back to work and stop wasting my day in pointless bickering and re-hashing the past with you.... Your viewpoint is always right, its pointless... disengaging
-
-
-
-
-
-
-
JDog will probably go back to work but you'll still be here tying nonsense
-
-
-
-
-
-
-
-
-
I also need to get back to real work. Sad to see this allowed in dev chat.
-
-
-
-
-
Where is your insurance jdog? Who bonded you to make processes? You and Adam have a real problem I will wait for the report. Any one else who want to help clean up make things better? Speak up now I respect good developers. I tried to address this type of stuff last year. You complain about Adam yet you protected him. If there are things wrong with the code when I get to it. Well have a nice trip see you next fall.
-
bro... your so out of touch, I handed over control of the repos at the beginning of 2024... and have no admin / control over repos.... but, your wouldn't take any time to actually follow the ongoings since your always right and know best.. lol
-
man i dont know who left more times me or you hahaha
-
-
difference is I disengage... I dont quit channels when i'm done speaking, then join to ramble on more then leave again... thats your MO.. I simply say disengaging... but will admit, your triggering with all your false claims and accusations... so tough to not respond sometimes, but its for the best, cuz nothing positive ever comes out of your mouth except your "positive" about you being right about everything... lol
-
@ffmad maybe consider being a mod and enforcing some rules here.... lest you endorse this kinda rambling on forever nonsense.
-
if your too busy to moderate, appoint some who can (not asking, dont want admin)
-
rambling is not dangerous
-
-
-
-
-
-
-
-
-
-
-
-
Thanks for sharing your concern of other people using it by mistake. Maybe I should invent my own "fiat" code to prevent confusion from other users depending on it as continual valid btc-usd
- 19 March 2025 (1 messages)
-
- 21 March 2025 (4 messages)
-
Interesting…. Javier n I got p2sh working n signing txs fine on counterparty-classic using bitcoin 28.1 (latest release)…. Which means that p2sh works fine on latest versions of bitcoin, with no changes to counterparty-classic codebase…. Yet counterparty-core has issues with p2sh, which Adam n Ouziel wrongly blamed on Bitcoin changes.
P2SH mpma send broadcast n parsed on Bitcoin 28.1:
https://classic.tokenscan.io/tx/2974857
Counterparty-core disabling p2sh n blaming bitcoin changes:
https://github.com/CounterpartyXCP/counterparty-core/issues/2632
We will be putting out an updated version of counterparty-classic 9.62.1 next week, which uses testnet4 instead of testnet3, and which runs on the latest version of Bitcoin 28.1 with NO loss of functionality and with p2sh encoding continuing to work perfectly fine.
TLDR, counterparty-core devs disabled p2sh encoding unnecessarily (used by MPMA sends) and forced users to the much more expensive multisig encoding, blaming bitcoin for the change, and indicated it’s all ok cuz taproot will be cheaper in the future🤷🏻♂️😂Protocol Change Proposal: Disable P2SH · Issue #2632 · CounterpartyXCP/counterparty-coreOur P2SH encoding no longer works with recent versions of Bitcoin Core. It was disabled in the API in October (because it was causing loss of user funds). There are multiple other bugs in the P2SH ...
-
FYI…. Interesting that counterparty-classic has no issues with p2sh yet counterparty-core does🤷🏻♂️
-
🤪 clueless.....like none of you know what's going on. The whole space is bullshit clown show. What's interesting is watching the lengths you go to and for what ?
-
The lengths we go to, and for what? To keep transactions cheap for end users, and hold devs accountable for misleading information obviously. 😂
FYI, it wasn’t that tough, just updated to the latest version of Bitcoin and tried to do a transaction on counterparty classic, and had no problems🤷🏻♂️
That’s OK houston, we know your MO, threaten everyone with legal action using funky, tribal jurisdiction law… one could ask you the same question as to why you go to such lengths…. Yet I don’t really care to know.
Have a nice day Houston…. Good luck building with stack😂 - 31 March 2025 (1 messages)
-
Joined.