- 02 July 2023 (3 messages)
-
Joined. -
helloo
Was wondering if anyone could see where I have gone wrong in this CP TX at all?
https://www.xcp.dev/tx/8f4fe5360fc8401600bf2a2224bc325e1c9ea5f9b7e9b0d48407982cd84ec3c0
doesnt seem to have been added to message streams but on glance seems like it has what it needs
Thanks in advance for any clues -
I tried the same TX again, but less complicated - no keyburn arguments and no 'send ownership' and it worked
https://xchain.io/tx/02317150099c1a1159a01d98fce6680950c3e7c2602e0339556f0fba99d86e88
So will dig in that area to see which item might have caused it, any clues still appreciated tho if anyone spots it :D - 03 July 2023 (14 messages)
-
It’s because you used the Counterparty burn address -
So as it went through validation steps it first saw you sending dust to Counterparty burn address and registered as an invalid burn
-
Ahah, I was trying to burn ownership along the way- I’ll see if it lets me get away with another burn address - thank you for the info joe!
-
burn address != keyburn -
Absolutely - was combo-ing a lot of gubbins here
-
This particular attempt was a issuance creation, token ownership transfer, keyburn and lock
-
Was confused because it had allowed this under a non ‘1counterpartyxxxxxx’ addy before and didn’t realise it would treat this differently
-
ahh
-
So was not sure if I screwed it in some new and wonderful way or not lol
-
that's a very special burn adddress
-
try it with 1BurnPepe type burn sadness znd should be possible
-
Yeh I can see what it might be treated different but just didn’t know that it would
-
Will
Do -
just coming back on that, an identical 'kitchen sink' style issuance function was possible after replacing the 1Counterpartyxxx Address - as y'all expected - thanks for that :D
- 04 July 2023 (27 messages)
-
So I have updated my node to 9.60.2 and I notice none of my hashes match xcp.dev ... What is the best way to fix this ?
Do I need to delete my counterparty DB and start over..e.g. re parse from the beginning? -
What fednode software you used? -
I had the std fednode install from 2022
-
so I did a fednode update from whatever version it was to 9.60.2
-
I can’t help much as I’m not using the “official” fednode
-
part of me thinks I should do a nobootstrap fresh setup .. the ol don't trust option
-
There was a bootstrap issue at one point due to a modified bitcoinlib but it should have been fixed, I’m running 9.60.2 with matching hashes to xcp.dev
-
can I just delete the cp DB file ? n cause it to re build ... would save my box from re syncing bitcoin n addrindexrs
-
Yes you don’t need to resync bitcoin and addrrindx
-
my bitcoin node seems to be having issues.. keeps loading addresses from dns seed it says when I fednode tail bitcoin
-
I also got an unhandled exception when it extracted the counterparty DB and checked for foreign keys
-
I wonder if I have a HDD hardware issue?
-
in the last 15 mins I have received just 9 blocks ..from 979122 to 979130
-
it should be churning through bitcoin blocks .., its a i5 6600 with 32gb ram on a good cable Internet connection
-
and again .. unhandleld exception ... malformed database schema when it does foreign key check
-
Keep counterparty stopped until bitcoin and addrindx are synced.
What do you mean with “extracted the counterparty db”? -
that's what the fednode tail counterparty said after I deleted the dB and caused it to download the bootstrap
-
it downloaded it ..extracted it and then crashed
-
Oh ok. You might need to fednode rebuild counterparty or something like that with fednode commands
-
I have deleted my 'federatednode' folder and re run the git clone command to kinda start afresh ... I kept the docker volumes .. run
fednode install full master -
-
Fyi full will install a bunch of unnecessary stuff
-
I can't get a --no-bootstrap to work
-
I want counterwallet to play about with as I want to make a multisig pwa app
-
so want to compare the multisig addresses I make using coinb.in javascript code in my pwa
-
I did a fednode stop and then fednode start bitcoin so bitcoin is only service I got running and it's processing blocks at a better rate .. am upto 797155 ... will let it get to tip and then bring up the addrindexrs and get that syncd ...and then try counterparty service
-
OK it's now running counterparty with fresh bootstrap download and processing transactions . block 794498 .. so a few thousand to go before I can check my hashes with xcpdev
- 05 July 2023 (1 messages)
-
Got my sync done and hashes matching 👍
- 13 July 2023 (14 messages)
-
Joined. -
Hey guys :) Are you all Bitcoin Core developers or is this some Bitcoin-Fork group?
-
Welcome Eli. Here we are working with Bitcoin (Core), not a fork.
See pinned messages, which show the open source Counterparty explorer xcp.dev, where you can verify the block hashes. -
A simple wallet script (based on counterwallet) has been open sourced: https://github.com/CNTRPRTY/simplestGitHub - CNTRPRTY/simplest: A simple bitcoin wallet script to use with counterparty
A simple bitcoin wallet script to use with counterparty - GitHub - CNTRPRTY/simplest: A simple bitcoin wallet script to use with counterparty
-
None
-
Also, xcp.dev has been updated! It now has access to market data (dispensers and orders) and the wallet section can now generate (some) transactions!
-
And finally announcing that bitST.ART has also been updated with ORD art!
Will appreciate your feedback -
Thanks :)
-
-
I came up with an idea this morning and wanted to get some feedback. Maybe someone is interested to read this. Be warned, might be useless / total garbage :)
-
i’d suggest putting it in a static google doc or something so no one has to download a pdf
-
True, will do that
-
Read it and it seems interesting, but I can’t give much more feedback as I’m not using nostr yet
-
- 15 July 2023 (2 messages)
-
https://github.com/CounterpartyXCP/cips/pull/99#issuecomment-1635833836
Taproot address CIP draft.
I've pointed out some revisions I think are necessary before accepting it as an official CIP.
What do you guys think? If most of you think it's good enough as is, i will add it now.- Added support for taproot cip by pataegrillo · Pull Request #99 · CounterpartyXCP/cipsCounterparty Improvement Proposals. Contribute to CounterpartyXCP/cips development by creating an account on GitHub.
-
Thanks for sharing, I made some comments
- 18 July 2023 (1 messages)
- 19 July 2023 (1 messages)
- 21 July 2023 (2 messages)
-
I opened a discussion for cip 30.
I suggest one month for discussions before polling the community.
If you have objections or concerns, please post it there for documentation.
https://github.com/CounterpartyXCP/cips/discussions/101CIP 30: Taproot Address Format · CounterpartyXCP/cips · Discussion #101Discuss CIP30: Taproot Support here. Please stay on topic and be respectful. Is there anything in the proposal that is unclear or needs clarification? Objections or concerns should be documented he...
-
@uanbtc please repost your comment on bitcoin version compatibility. Good to have this documented in the main discussion thread.
- 22 July 2023 (1 messages)
-
Done
- 23 July 2023 (1 messages)
-
Left.
- 25 July 2023 (7 messages)
-
Are these instructions still good? Any recommendations for an idiot like me who refuses to use docker? VM’s for the win for me. -
They work, but if you use the cntrprty option, the current master has some database schema optimizations which are generating the same txlist_hash, but not the same hashes for the ledger and messages. And this node is also on bitcoin core v0.21.1
I’m not sure what is causing the different hashes and would like to learn why… -
that should be fixed, my ledger hashes match yours and im running the latest v9.60.2
-
Yeah cntrprty also updated to v9.60.2, BUT then the code also has the additional differences mentioned
-
those differences shouldn’t affect hashes
-
@ABlue0ne just fixed the master branch to not include the db schema change, which now is in https://github.com/CNTRPRTY/counterparty-lib/commits/txhash_0211Commits · CNTRPRTY/counterparty-lib
Counterparty Protocol Reference Implementation - Core Version - Don't trust, verify - Commits · CNTRPRTY/counterparty-lib
- 26 July 2023 (1 messages)
-
Left. - 27 July 2023 (3 messages)
-
Left.
-
too many bots XD -
Left.
- 28 July 2023 (1 messages)
-
Left.
