- 01 April 2024 (59 messages)
-
Gm! Were you able to find the cause of the difference in our message index? -
-
Still not kickstarting with manual installation.
My issues were the bitcoind chainstate directory has an assumed parent directory and addrindexrs version mismatch (I somehow installed a newer version of addrindexrs than required in the code check)
What do you recommend for a manual install? -
Your documentation is great. Nice details. Keep up the good work.
-
@teysol Could counterwallet get the same MIT license as the rest of the project? Github has no license for Counterwallet at the moment.
-
Kickstart failed with a check. Expected 4.4.4 or 0.4.4. Afk right now.
-
Thx. So I will need to rerun from the start? 🙂
-
I can check and/or execute any suggestions tomorrow and report back. Let me know if you want me to run any commands or check logs/versions.
-
i rollback this and now syncing again, updated in the way addrindexr as it was in a previous version -
mmmm i think the last one, not sure how to chek, i am in master in the repo, but as its pulling images from docker and not comiling the current code in the repo not sure
-
it says latest ues
-
in the docker image
-
let me check what says docker.io about
-
-
thats what dockerhub says i think should be -rc.2?
-
i hope so lol
-
but anyway im super happy is thousands times fastest than before
-
great job guys
-
im 500 blocks away of the missmatch so i let you know
-
no ser, start, but faster anyway
-
as i had many blocks indexed and wanted to check if that rollback fixes the issue i didnt tested the kickstart for docker yet
-
nice
-
i have one question regarding docker image generation, as i see it is in the github ci workflow but here has failed, it will be automatic each release?
-
i am planning to create a simplenode extended with the stamps indexer to easy deployment in all the machines and i would like to know what should be the process when a new version is detected, my unerstanding is that reparse counterparty db is enough but maybe im wrong
-
also, passed the missmatch block without issues, thanks :D
-
okey will see how to automatice it
-
Thanks ser
- 02 April 2024 (53 messages)
-
Thanks for the reply. I was looking over the counterwallet github and noticed there was no license chosen in the normal github license location, is the reason I said anything. I was looking for one and didn’t find it where I expected. Any license is what I was looking for, you all are the ones qualified and entitled to make the decisions about the licenses. Thanks.
-
hello! im full synced, but im having issues to interact with counterparty api using docker
-
has anyone experienced this error?
-
i cannot reach port 4000 within the machine or with the external one, but for example i can connect without problems with bitcoind
-
yes, just changed the ip value as i was getting errors, will pull and try again with last oficial one
-
was using simplenode one
-
looks like now it works
-
going to do some tests
-
thanks for the headsup
-
Docker can have problems with 127.0.0.1 vs localhost and working with dependencies that prefer one over the other.
-
another question, has changed the api responses for the bindings object in the get_blocks response under the _messages ??
-
yes... looks like has changed and now instead of return a json object with all the data returns just an array with the keys
-
NEW RESPONSE for {
"method": "get_blocks",
"params": {
"block_indexes": [779652]
},
"jsonrpc": "2.0",
"id": 0
}
{
"result": [
{
"block_index": 779652,
"block_hash": "00000000000000000002ea8eb5df114c3f198c7ef5851435e8a4d8e7bd33121c",
"block_time": 1678151949,
"previous_block_hash": "00000000000000000002124201cb18fe9fcbeb071115ac863f3d194469081376",
"difficulty": 43053844193928.45,
"ledger_hash": "2dd9dbd7b7edea619889f3584d318527936986037124b9c8f71faebc11584d24",
"txlist_hash": "b68c784f9ccac2548241c2920ac1819f6df1b7e8306db593edd6204d7af65449",
"messages_hash": "ecaa0e79eb8ff2529c5ca4653d6d9d80098e87f20f3020a6fc7208ce1b92196a",
"_messages": [
{
"message_index": 4430651,
"block_index": 779652,
"command": "insert",
"category": "sends",
"bindings": "['asset', 'block_index', 'destination', 'memo', 'quantity', 'source', 'status', 'tx_hash', 'tx_index']",
"timestamp": 1711554031,
"event": null
},
{
"message_index": 4430652,
"block_index": 779652,
"command": "insert",
"category": "issuances",
"bindings": "['asset', 'asset_longname', 'block_index', 'call_date', 'call_price', 'callable', 'description', 'divisible', 'fee_paid', 'issuer', 'locked', 'quantity', 'reset', 'source', 'status', 'transfer', 'tx_hash', 'tx_index']",
"timestamp": 1711554031,
"event": null
},
{
"message_index": 4430653,
"block_index": 779652,
"command": "insert",
"category": "issuances",
"bindings": "['asset', 'asset_longname', 'block_index', 'call_date', 'call_price', 'callable', 'description', 'divisible', 'fee_paid', 'issuer', 'locked', 'quantity', 'reset', 'source', 'status', 'transfer', 'tx_hash', 'tx_index']",
"timestamp": 1711554031,
"event": null
},
{
"message_index": 4430654,
"block_index": 779652,
"command": "insert",
"category": "sends",
"bindings": "['asset', 'block_index', 'destination', 'memo', 'quantity', 'source', 'status', 'tx_hash', 'tx_index']",
"timestamp": 1711554032,
"event": null
},
{
"message_index": 4430655,
"block_index": 779652,
"command": "insert",
"category": "sends",
"bindings": "['asset', 'block_index', 'destination', 'memo', 'quantity', 'source', 'status', 'tx_hash', 'tx_index']",
"timestamp": 1711554032,
"event": null
}
]
}
],
"id": 0,
"jsonrpc": "2.0"
} -
PREVIOUS RESPONSE:
{
"result": [
{
"block_index": 779652,
"block_hash": "00000000000000000002ea8eb5df114c3f198c7ef5851435e8a4d8e7bd33121c",
"block_time": 1678151949,
"previous_block_hash": "00000000000000000002124201cb18fe9fcbeb071115ac863f3d194469081376",
"difficulty": 43053844193928.45,
"ledger_hash": "2dd9dbd7b7edea619889f3584d318527936986037124b9c8f71faebc11584d24",
"txlist_hash": "b68c784f9ccac2548241c2920ac1819f6df1b7e8306db593edd6204d7af65449",
"messages_hash": "0c1791a755c55e765aadbbb3cef969e7c79c58610862e6f4e9dd21be652e7e0f",
"_messages": [
{
"message_index": 9123590,
"block_index": 779652,
"command": "insert",
"category": "debits",
"bindings": "{\"action\": \"send\", \"address\": \"1KDf6ZbetZfWqeQmCddupnjMnQN7fZTiiB\", \"asset\": \"WOJAKPARTY\", \"block_index\": 779652, \"event\": \"3c9d2e9c3f46b6f053ff27e7a9d57c963550cc58ca49c9e95cc3b2fd69200970\", \"quantity\": 1}",
"timestamp": 1705309510
},
{
"message_index": 9123591,
"block_index": 779652,
"command": "insert",
"category": "credits",
"bindings": "{\"action\": \"send\", \"address\": \"1CCPbFbST8ruJrTGjm2Ss5aTAaqng4naBN\", \"asset\": \"WOJAKPARTY\", \"block_index\": 779652, \"event\": \"3c9d2e9c3f46b6f053ff27e7a9d57c963550cc58ca49c9e95cc3b2fd69200970\", \"quantity\": 1}",
"timestamp": 1705309510
},
{
"message_index": 9123592,
"block_index": 779652,
"command": "insert",
"category": "sends",
"bindings": "{\"asset\": \"WOJAKPARTY\", \"block_index\": 779652, \"destination\": \"1CCPbFbST8ruJrTGjm2Ss5aTAaqng4naBN\", \"memo\": null, \"quantity\": 1, \"source\": \"1KDf6ZbetZfWqeQmCddupnjMnQN7fZTiiB\", \"status\": \"valid\", \"tx_hash\": \"3c9d2e9c3f46b6f053ff27e7a9d57c963550cc58ca49c9e95cc3b2fd69200970\", \"tx_index\": 2262967}",
"timestamp": 1705309510
},
{
"message_index": 9123593,
"block_index": 779652,
"command": "insert",
"category": "debits",
"bindings": "{\"action\": \"issuance fee\", \"address\": \"1GotRejB6XsGgMsM79TvcypeanDJRJbMtg\", \"asset\": \"XCP\", \"block_index\": 779652, \"event\": \"17686488353b65b128d19031240478ba50f1387d0ea7e5f188ea7fda78ea06f4\", \"quantity\": 0}",
"timestamp": 1705309510
},
{
"message_index": 9123594,
"block_index": 779652,
"command": "insert",
"category": "issuances",
"bindings": "{\"asset\": \"A7337447728884561000\", \"asset_longname\": null, \"block_index\": 779652, \"call_date\": 0, \"call_price\": 0.0, \"callable\": false, \"description\": \"stamp:iVBORw0KGgoAAAANSUhEUgAAAAUAAAAFCAYAAACNbyblAAAAHElEQVQI12P4//8/w38GIAXDIBKE0DHxgljNBAAO9TXL0Y4OHwAAAABJRU5ErkJggg==\", \"divisible\": false, \"fee_paid\": 0, \"issuer\": \"1GotRejB6XsGgMsM79TvcypeanDJRJbMtg\", \"locked\": false, \"quantity\": 1, \"reset\": false, \"source\": \"1GotRejB6XsGgMsM79TvcypeanDJRJbMtg\", \"status\": \"valid\", \"transfer\": false, \"tx_hash\": \"17686488353b65b128d19031240478ba50f1387d0ea7e5f188ea7fda78ea06f4\", \"tx_index\": 2262968}",
"timestamp": 1705309510
},
{
"message_index": 9123595,
"block_index": 779652,
"command": "insert",
"category": "credits",
"bindings": "{\"action\": \"issuance\", \"address\": \"1GotRejB6XsGgMsM79TvcypeanDJRJbMtg\", \"asset\": \"A7337447728884561000\", \"block_index\": 779652, \"event\": \"17686488353b65b128d19031240478ba50f1387d0ea7e5f188ea7fda78ea06f4\", \"quantity\": 1}",
"timestamp": 1705309510
},
{
"message_index": 9123596,
"block_index": 779652,
"command": "insert",
"category": "debits", -
is this intentional? or is it a bug?
-
also i see less entries in one response than another, looks like debits and credits are not being there anymore?
-
going to open a Issue on github regarding this
-
Major api changes on get_blocks · Issue #1587 · CounterpartyXCP/counterparty-core
Hello looks like there is son issue in the api: For the method: { "method": "get_blocks", "params": { "block_indexes": [779652] }, "jsonrpc": "...
-
@XJA77 thank you for being ahead. My simplenode has been in the 600k for 3 days now 😔
The bindings with values are expected, and what actually make the messages table be reliable as a single source of truth.
Can you check if the ‘command’ has update, and is not always insert? -
looks like this is a fixed bug as @teysol mentions in the issue, maybe not updated in the docker image as i saw that sometimes didn't push good to docker hub, and yes will check but at the moment i just see inserts, in which case should be an update so i can find more specific? what im seeing is that debit and credits has disapeared in this new version
-
also now im not using the simplenode, im using the last docker-compose.yml file in the root of the repo, looks like simplenode folder doesnt exists anymore on the repo, i had to trick it to add the new info of docker-compose in to the simplenode/compose.yml file as i didnt wanted to loose my sync there
-
Yes with the new docker there is no reason to continue running mine. Is also old code by now
-
@teysol are credits and debits being included in the fixed code?
-
-
but in the new version there are not insert credit and insert debit messages
-
neither in get_blocks or get_messages call
-
i thought the API wasnt changing for this new release -
just one question, maybe stupid one,doesnt makes sense havve the api as a different service? so makes easier to made changes without need to impact the core code?
-
okey
-
In my view, for Counterparty, something like this can make a lot of sense.
I believe the core reference implementation protocol can focus mostly on the block parsing. Maybe include a basic http api.
But mostly delegate the responsibility of HOW to read the DB tables to the applications.
In essence, the main consensus is a hash. Then, data produces this hash. The data is in a DB. So, the interface is the DB. The http api is an additional layer of interface.
My opinion. -
I just updated to rc.1 and I am still getting this error when kickstarting.
I believe it MAY be related to my bitcoind install storing blocks in a different folder than default while counterparty is using an assumed root directory to locate ../chainstate/, maybe. Counterparty is assuming that /blocks and /chainstate have the same root. In my instance they do not, but it is ok to run bitcoind that way and it is supported by bitcoin.conf via the blocksdir= option and not too uncommon.
blue@blue:~/counterparty-core$ counterparty-server --version
counterparty-server v10.0.0-rc.1; counterparty-lib v10.0.0-rc.1
blue@blue:~/counterparty-core$ counterparty-server kickstart
Running v10.0.0-rc.1 of Counterparty Core.
Configuration file: /home/blue/.config/counterparty/server.conf
Counterparty database: /home/blue/.local/share/counterparty/counterparty.db
Writing log to file: /home/blue/.cache/counterparty/log/server.log
Writing API accesses log to file: /home/blue/.cache/counterparty/log/server.access.log
------------------------------ kickstart ------------------------------
Warnings:
- Ensure addrindexrs is running and up to date.
- Ensure that bitcoind is stopped.
- The initialization may take a while.
Proceed with the initialization? (y/N): y
[OK] Connecting to addrindexrs...
[OK] Getting last known block hash...
[= ] Checking database state...ERROR:root:SQLITE_LOG: recovered 31 frames from WAL file /home/blue/.local/share/counterparty/counterparty.db-wal (283) SQLITE_NOTICE_RECOVER_WAL
[OK] Checking database state...
[OK] Backing up database...
Unhandled Exception
Traceback (most recent call last):
File "/home/blue/.local/bin/counterparty-server", line 8, in <module>
sys.exit(server_main())
^^^^^^^^^^^^^
File "/home/blue/.local/lib/python3.11/site-packages/counterpartycli/__init__.py", line 20, in server_main
server.main()
File "/home/blue/.local/lib/python3.11/site-packages/counterpartycli/server.py", line 223, in main
server.kickstart(
File "/home/blue/.local/lib/python3.11/site-packages/counterpartylib/server.py", line 557, in kickstart
kickstarter.run(
File "/home/blue/.local/lib/python3.11/site-packages/counterpartylib/lib/kickstart/__init__.py", line 352, in run
kickstart_db, block_count, tx_index, last_parsed_block = intialize_kickstart_db(
^^^^^^^^^^^^^^^^^^^^^^^
File "/home/blue/.local/lib/python3.11/site-packages/counterpartylib/lib/kickstart/__init__.py", line 184, in intialize_kickstart_db
first_kickstart_block = cursor.execute('SELECT block_index FROM kickstart_blocks ORDER BY block_index LIMIT 1').fetchone()['block_index']
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not subscriptable
Is there something I can do to help diagnose? I’m willing to try and can make small code changes on my side if anyone has suggestions. -
Chainstate is now symlinked and files are where counterparty is looking. Still same error.
-
See above, I typed an update while you typed this response. There is now a symlink. Counterparty should not know the difference anymore.
-
‘NoneType object error is not subscriptable’ does not point towards my setup config but rather a variable returning None when something else is expected.
Definitely dont block a release but production servers and security minded setups typically have idiosyncratic setups.
I’m game to debug, let me know what to check/do if/when you’re interested. I’ll leave github comments and tickets alone until I can run a node. -
Deleting db helps by getting fresh errors instead of same old.
Blocks folder and chainstate are answering where they should via symlink to make counterparty happy; I keep getting other ‘NoneType’ object not subscriptable errors.
What old version is installable manually? - 03 April 2024 (69 messages)
-
I see in the readme 1.5TB as minimum. How close is this to the actual DB sizes? In current nodes 1TB is enough…
-
Also reading that the docker compose uses the bootstrap…
-
For me it has not used it I think as has took 6 - 7 days and as I have understood with bootstrap takes less?
-
Joined. -
Then I’ll see how far I can get with my current test setup, since is bootstrap anyway
-
is this normal logs when doing a reparse? i thought that was more dynamic logs
-
hard to know if is still working
-
ah okey
-
perfect thanks ser
-
it is there foralmos half an hour
-
ah noo looks like it is moving, the [ ==]
-
No... Text still in same step
-
Just the "loading bar" still moving sometimes
-
I like tqdm python lib for loops, shows cool process bars with steps left
-
That's the tail of the logs
-
Ah okey you mean the log file? Okey will check it
-
here shows more info yes, thanks ser
-
let see how much takes, at least i see is still working so matter of patience
-
this is what I get when I click on those links (and bypass a cert error)
-
Did you get v10 running without docker?
-
Also would be good to have a website that tracks public and private nodes available
-
So you can register your node, and if you want it to be public or not but as a way to track consensus and posible add notifications
-
So you know if your node is still on consensus with the network
-
If I remember good Juan in his apis calls return some data about the node version
-
Now is just part of the url, but is also at the “version root” https://api.xcp.dev/v9_61/
-
That's cool too
-
So whenever someone enters in that webpage it calls the different node list and gets the important data (is online, node version, latency, etc)
-
@uanbtc Do you have a copy of 9.60 that can be installed manually? I want to work on the SPA while waiting on v10 The rename of the repo from cli to core removed the github link for old versions, I think.
-
If you want to work on the react app you can just run it locally. Use the same api endpoints as the current 960.xcp.dev website. No need to run your own server.
Or is there a specific reason you also want to run the backend? -
Thanks for that. Changing api.js api_host results in about 75% functionality on the spa, with ‘issuances’ bringing up errors or no results at Asset.fetchData bundje.js 3107:54
I think there is a proxy setting somewhere I need to set also. Or api.js was the wrong place to start changing hosts. -
So you got the frontend running locally, and you see that error where? The api shouldn’t return an error like that
-
The frontend running locally. Loading the spa locally in chrome from IDE opens home page successfully, but block transactions stays at loading. some pages/functions say 404 in their div (dispensers open/closed for example) some functions like asset details return runtime error basically saying spa is expecting its resources from localhost. I only changed the host in api.js. Is there a config location/file I’m missing?
-
First confirm whatever you are trying does work in current production.
You must be in develop branch commit 31ae8b3 to have the same code as the website. Except for missing values in api.js. The main one being:
const api_host = "https://97bhdwc2g0.execute-api.us-east-1.amazonaws.com";
Wallet create stuff won’t work though. -
That aws api host is resulting in expected spa behavior. I was using https://api.xcp.dev/v9_61 and getting partial success.
-
Yeah spa is using the old api. The most up to date code (the default xcp.dev) is in the genesis repo
- 04 April 2024 (28 messages)
-
I just pulled updates, counterpartywallet looks new. Is this counterwallet renamed and updated?
-
Counterparty-core, I pulled and saw counterparty-wallet created files.
-
I almost tagged you in that first comment but didnt want to bother you.
-
Cool. Better than nothing. Thanks.
-
Tried this json post body:
{
"method": "get_running_info",
"params": {}
}
To https://nodes.blockvault.ai/counterparty
And got this response:
{
"code": -32600,
"message": "Invalid Request",
"data": "Invalid JSON-RPC 2.0 request format"
} -
Got it, thanks!
-
Following up here. Yes, updates are still showing in as command! Awesome
-
I’m guessing you aren’t a fan of manual install and I understand the status of the code… fwiw here is some feedback from manual install/upgrade on Debian LTS today…
Commit 9b66701 v10.0.1
After pulling updates and reinstalling, kickstart fails with no on screen errors, errors were on screen before.
Tailing the log shows NoneType object not subscriptable error re: lib/backend/addrindexrs.py line 469 index_check_version
It appears that force=0 or 1 changes nothing with my situation. Also appears that no connection is made to addrindexrs where (i think) previously kickstart attempts did connect to addrindexrs, or at least tried and showed something when tailing addrindexrs, but nothing now.
‘Start’ does not work any more, but did for me prior to today, it was just slow. Throws the same error now as kickstart.
‘Start’ is not taking —bitcoind-dir= option at all. @XJA77 you had a docker issue/question about something similar above, it might not be a docker only problem.
Lmk if you have questions that can help you, the project or the team. Thanks. -
I’m planning on doing the manual install so all your notes will be greatly appreciated! Have you made an issue or pr about these?
-
Not yet. Maybe when I get a better idea on the errors. I could copy paste the above if that would help.
-
You can just make a general “manual install experience” issue I guess.
Start with your machine specs and OS, add the commands you have used, etc… -
Done
-
Is the genesis repo the same as SPA but without Johns eye candy?
-
Genesis is the original single repo with everything, web app and simple api backend.
Spa is a fork, only focusing on the single page application. Api is also a fork, focusing only on the api.
I’ve continued to work on the original (now genesis). The forks may get updated by me, but not sure when. Others are free to contribute obviously.
To note is that at the time of the forks the code still didn’t have a license. Now genesis has an Unlicense license. -
im restarting everything following this: https://github.com/CounterpartyXCP/Documentation/blob/bc5416136e3b6797fc6eed60bbd5619895ce83b1/docs/advanced/how-to/docker-kickstart.md i let you know how it goesDocumentation/docs/advanced/how-to/docker-kickstart.md at bc5416136e3b6797fc6eed60bbd5619895ce83b1 · CounterpartyXCP/Documentation
Official Documentation of the Counterparty Project - CounterpartyXCP/Documentation
-
Version checking is failingish when installing Ouziel’s commit 0c18c2 from today. I get dependency error that cp-cli 10.0.0rc1 is looking for cp-lib==10.0.0-rc.1 but you have cp-lib 10.0.0 and is incompatible. @teysol
-
When manually installing lib
- 05 April 2024 (9 messages)
-
Fresh pull to 0c18c2 and I see -core, -lib, -rs, -wallet. No -cli folder in develop branch. Let me rm and pull master.
-
any idea?
2024-04-05-T16:01:45+0000 [DEBUG] Opening socket to address indexer at `172.17.0.3:8432`
2024-04-05-T16:01:45+0000 [DEBUG] Connection refused by addrindexrs. Trying again in 8 seconds.
2024-04-05-T16:01:53+0000 [DEBUG] Opening socket to address indexer at `172.17.0.3:8432`
2024-04-05-T16:01:53+0000 [DEBUG] Connection refused by addrindexrs. Trying again in 8 seconds.
2024-04-05-T16:02:01+0000 [DEBUG] Opening socket to address indexer at `172.17.0.3:8432`
2024-04-05-T16:02:01+0000 [DEBUG] Connection refused by addrindexrs. Trying again in 8 seconds.
2024-04-05-T16:02:09+0000 [DEBUG] Opening socket to address indexer at `172.17.0.3:8432`
2024-04-05-T16:02:09+0000 [DEBUG] Connection refused by addrindexrs. Trying again in 8 seconds.
2024-04-05-T16:02:17+0000 [DEBUG] Opening socket to address indexer at `172.17.0.3:8432`
2024-04-05-T16:02:17+0000 [DEBUG] Connection refused by addrindexrs. Trying again in 8 seconds.
2024-04-05-T16:02:25+0000 [DEBUG] Opening socket to address indexer at `172.17.0.3:8432`
2024-04-05-T16:02:25+0000 [DEBUG] Connection refused by addrindexrs. Trying again in 8 seconds.
2024-04-05-T16:02:33+0000 [DEBUG] Opening socket to address indexer at `172.17.0.3:8432`
2024-04-05-T16:02:33+0000 [DEBUG] Connection refused by addrindexrs. Trying again in 8 seconds. -
FWIW and documentation notes: on develop fresh pull there are -core, -lib, -rs, -wallet folders.
The develop readme points to surface web for docs.
Master readme says install -rs, -lib, -cli in that order. Readmes will need a small update. - 06 April 2024 (3 messages)
-
only the first input matters
-
Node fully synced, using 808GB
- 08 April 2024 (22 messages)
-
xcp.dev has been updated!
Mobile optimized and with dark mode. The wallet functionality is back also.
Thanks to @Chriton for leading the way into using tailwind.js, and for some design choices.
The work by John at 960.xcp.dev will most likely stay as is, but fortunately it was used and expanded in stampverse.io.
And this is actually one of the main purposes of the xcpdev project, using its open/free/libre code as a foundation to build on top of. -
Not the data, but in some places the presentation of the data *could* be considered as sanitizing it… what are you referring to specifically?
-
The api is straight from the SQLite DB. On the front end I do clean up a bit
-
99% is read only. The wallet is the only place where user input is used, and is still very basic with just a few methods and no private key involved. But thanks for the heads up!
-
I’ll appreciate it! Just a single post in the api backend, so anything there that can be improved let me know here or in the repo itself
https://github.com/CNTRPRTY/xcpdev-genesis/blob/48ba3b3a1aca8ab04a70e75be0c2758449bf581b/server/express_server/src/index.js#L554xcpdev-genesis/server/express_server/src/index.js at 48ba3b3a1aca8ab04a70e75be0c2758449bf581b · CNTRPRTY/xcpdev-genesisOpen Counterparty Bitcoin Data Explorer - DIY Node - CNTRPRTY/xcpdev-genesis
-
looks like a user is having an issue with an MPMA send not showing up in the xcp database (using recent OSx version of 0.9.29)
https://blockstream.info/tx/28bd1626a21d6a5ccae60dd9b44ad95580dba829114a6dfef81b4e60cafb4bde
looks like the tx is confirmed but xchain dot io, xcp dot io are not seeing it as valid.... but xcp dot dev does...Blockstream Block ExplorerBlockstream Explorer is an open source block explorer providing detailed blockchain data across Bitcoin, Testnet, and Liquid. Supports Tor and tracking-free.
-
wallet used above was Freewallet Desktop ^
is there a tool you guys recommend for checking OP_RETURN info? decoding the HEX to see the function the user inputed? -
You can see the hex of the transaction here, which was stored on the Counterparty DB:
https://www.xcp.dev/tx/28bd1626a21d6a5ccae60dd9b44ad95580dba829114a6dfef81b4e60cafb4bde
But there were no messages stored. And after further debug, no entries in the sends table either.
This is a bug in the protocol it seems, maybe is an invalid mpma send. There should at least be an insert of the invalid send (and its entry in the messages table).
The decoding of the hex for mpma transactions is not yet done in xcpdev, but it should be added and it would have been very helpful in a case like this. -
awesome thanks for the response, good to know thats how you are reading it (protocol issue) - couldnt find anything wrong on my end reading the data
-
or just a malformed message, its difficult to decode MPMA data manually
-
we tried to rule that out - and using the recent versions of FW - the wallet wont let you send invalid entries - for instance if I wrote out "address, token, amount, memo" without the spaces in between, FW will reform the data into something valid (and add the spaces for you)
-
Yeah the protocol should handle it better, but maybe the source problem is client side
-
ill wait for jdog to look over and let you know
-
Still, you should file an issue in the repo
-
MPMA issue with confirmed btc tx using Freewallet 0.9.29 · Issue #1609 · CounterpartyXCP/counterparty-core
looks like a user is having an issue with an MPMA send not showing up in the xcp database (using most recent version Mac OSx Freewallet Desktop version of 0.9.29) Steps to reproduce the behavior us...
- 09 April 2024 (45 messages)
-
gm! I have counterparty v10.0.0-beta.1 and addrindexrs v0.4.4, what's the best way to update? Git pull the latest then reparse counterparty?
-
so restart from the beginning and do fast sync?
-
feels good man
-
how do you udpate addrindexrs? I got the latest version then built and relaunch but counterparty-server is telling me its still v0.4.4
-
this worked 👍
-
How is the upgrade procedure for docker installation? I just started testing yesterday, and I’m in version 10.0.0-rc.1.
And my initial impressions is that there seems to be some non-determinism in the messages table (among other things)… -
i still couldnt sync on this version :(
-
neither bootstrap kickstart or no bootstrap
-
gm, been away for a minute, I was thinking I would nuke my AWS and do a full start from the begining, do we and updated install doc for ubuntu -
v10.0 first impressions, differences to v9.61 · Issue #1614 · CounterpartyXCP/counterparty-core
Running v10.0.0-rc1, installed with Docker Compose following https://docs.counterparty.io/docs/basics/getting-started/. First of all just want to congratulate on the effort and work done to get to ...
-
The newest version/release ate the README.
-
-
I see you closed my issue on github with a message that says the readme sends users to the surface web, but the surface web readme install docs are also outdated. Manual install docs references -cli not -wallet for example.
Want me to make a new issue on github to clarify? -
Do a kickstart*
-
Avoid the classic start, it takes at least 5 days 😅
-
By removing the addrindexrs?
-
General question, is multiple versions of Counterparty, all based on a reference implementation, something we should aspire to or not?
-
Lightning network has multiple implementations
-
I’m not sure about the specifics of what they share, maybe nothing? And is all based on the initial white paper…
-
Bringing this up specifically because of the messages table / hash.
Thinking that maybe a better approach for that table should be having minimal (but critical) data thus allowing other implementations to replicate it.
If it takes the opposite direction of including as much implementation details as possible it would make it harder to reproduce the same hash… -
@teysol why the thumbs down?
-
At this stage, yes… maybe. It should not be a definite. Don’t trust, verify.
And I don’t understand why it should be as hard as possible to reproduce the hash… if you can elaborate that would be appreciated.
v9.61 does not have all tables as messages. Only a selection, which when analyzed, is minimal. For example, there are no blocks, transactions, assets… all which I am now seeing as messages in v10… -
For anyone interested, here is a version of xcpdev running v10:
http://v10.0.0-rc.1.preview.xcp.dev.s3-website-us-east-1.amazonaws.com
The changes to the code are in the repo (and I would appreciate any review, as I’m not getting the expected results at multiple places):
https://github.com/CNTRPRTY/xcpdev-genesis/tree/v10testsGitHub - CNTRPRTY/xcpdev-genesis at v10testsOpen Counterparty Bitcoin Data Explorer - DIY Node - GitHub - CNTRPRTY/xcpdev-genesis at v10tests
- 10 April 2024 (56 messages)
-
Any sync problems?
-
Looking into it now
-
Update pushed
-
-
Does anyone has updated his fednode
-
And knows how to do it?
-
i was expecting dont needing to do it but with the yesterday bug i wont have other option
-
I was thinking on load balance them yes
-
If you are using the federatednode there is no need to do this.
If you are using github.com/CNTRPRTY/federatednode:
Go to federatednode/src/counterparty-lib. Then git pull. Finally: fednode rebuild counterparty counterparty-testnet --no-cacheGitHub - CNTRPRTY/federatednode: Federated Node Build System - Core Version - Don't trust, verifyFederated Node Build System - Core Version - Don't trust, verify - CNTRPRTY/federatednode
-
Let's drop the "CP node" term too
-
If you incentivice all nodes are in consensus and if is in consensus you load balance them and when people ask for a writing function the selected node has some kind of incentive for resolving the writing tx (small fee) is a win win
-
There is no CP node. Just a Bitcoin node with CP interpreter
-
The node is Bitcoin, there is no CP node
-
Decentralize Counterparty 🤓
-
Periwig had the right term for this, but I can't remember what it is 😅
-
@teysol Periwig i don’t see rowid from query results.
https://github.com/CounterpartyXCP/counterparty-core/issues/1618Where is the rowid? · Issue #1618 · CounterpartyXCP/counterparty-coreRunning v10.0.0-rc1, installed with Docker Compose following https://docs.counterparty.io/docs/basics/getting-started/. Currently testing this version at http://v10.0.0-rc.1.preview.xcp.dev.s3-webs...
-
Joined. -
Gm ☕️
-
welcome ser
-
Thanks to @teysol for the quick fix!!!
-
Figured it out. Issue closed.
-
is the get_blocks call ded?
-
getting
"error": {
"code": -32000,
"message": "Server error",
"data": {
"type": "SQLError",
"args": [
"SQLError: row value misused"
],
"message": "SQLError: row value misused"
}
},
"id": 0,
"jsonrpc": "2.0"
} with v10 -
i can create an issue
-
Queries fixed!!! Showing same results in v9.61 and v10:
https://www.xcp.dev/asset/DAILYSMOL
http://v10.0.0-rc.1.preview.xcp.dev.s3-website-us-east-1.amazonaws.com/asset/DAILYSMOL -
Final boss PEPECASH may time out, but testing to my node directly is not too bad. With the cache integrated it should work just like the current xcp.dev.
So… I stand corrected. The new schema seems to have the appropriate indexes for read queries still being reasonably fast!
Very happy with these results and congratulations to the devs 🤓 - 11 April 2024 (12 messages)
-
Discovery, load balance and telematics should be opt-in.
-
open an issue
-
I think those servers have been updated to v10…
I notice that you are querying for an address starts with, is it because you are interested in multiple addresses?
You can check them individually in xcp.dev which is still running v9.61… maybe the api calls here can be useful to you, as it shows both open and closed dispensers for an address -
How do I rebuild and use 9.61.3. -
Do I checkout the branch basically
-
If you are running from github.com/CNTRPRTY, yes.Bitcoin and Counterparty Tools
Decentralizing CNTRPRTY: "Counterparty is Bitcoin. Is on top of Bitcoin. Is Web3. Is Web5. Two steps ahead." 🐸 - Bitcoin and Counterparty Tools
-
Not sure if is the same for the oficial repo
- 12 April 2024 (31 messages)
-
Ok, so if I have a fednode there's no upgrade path within that paradigm. I need to reroll?
-
I tried this:git remote -v
git remote set-url origin https://github.com/CounterpartyXCP/counterparty-core.gitgit remote -v
git fetch --tags git checkout v9.61.3
git pull
git fetch origingit reset --hard v9.61.3
git clean -fd
And then I ran this:fednode rebuild counterparty
But that installed the new version, so I guess rebuild isn't the move. Is it update or restart? -
I've got like a 10 XCP bounty for the chad who knows how to get the service to use the branch.
-
But that installed the new version as in v10?
-
I think so because when I tail counterparty after I get this error (in part):
Wrong addrindexrs version: 0.4.6 is needed but 0.4.1 was found
And I think v10 requires that version -
Hmmm do you have a way to revert? You running local or in a cloud provider?
-
In other words, did you backup before doing anything?
-
It's in da cloud
-
Backups for wimps
-
lol but you might be in a weird codebase with the commands you did…
Maybe go to federatednode/src and in each of those folders check the commit you are in. Then you’ll know where you stand and checkout to the versions you should be in each.
But the software might want to reparse… not sure what will happen -
git branch * (HEAD detached at v9.61.3)
-
Check the commit with git log
-
And do the same for addressindrs
-
ok so i guess i installed the lastest somehow doing what I did:
commit 69b91be86b8f0835981186b3f1ca04f5f11d183f (HEAD, tag: v9.61.3, tag: v10.0.1-2, tag: v10.0.1, origin/master, origin/HEAD) -
I think the issue is I tried to use the tags, but there's two. And one doesn't do what it says on the tin.
https://github.com/CounterpartyXCP/counterparty-core/releases/tag/v9.61.3
https://github.com/CounterpartyXCP/counterparty-core/releases/tag/v9.61.3-2Release v9.61.3 · CounterpartyXCP/counterparty-coreRelease Notes - Counterparty Core v9.61.3 (2024-04-09) ChangeLog Stability and Correctness Add missing sanity check in address unpacking for dispensers that causes a complete network crash Credit...
-
Checkout directly to the commit you want
-
I'm back in business doing what I did before but using "v9.61.3-2" instead of "v9.61.3".
-
Hit me with an address and I'll send you 10 XCP
-
I saw Adam mention it doesn't make sense to work on Counterblock.
-
Just sharing that this is where mine failed:
INFO:assets: Credit 1 A2737059176450433500 to 1CCMRNyv4zmGgr9eHHgMU2XcFtsPUqNohN (new bal: 1, msgID: 10198330) -
Block 820116
-
Mmmm that block looks familiar for me I think I had same issue in one of my runs
-
I know counterblock is a dependency for counterwallet. What does counterblock do?
-
Yes is working:
{
"result": {
"btc_in": 403250,
"btc_out": 69420,
"btc_change": 291948,
"btc_fee": 41882,
"tx_hex": "0200000000010186faad59fbe95a53e88914da84f4e9c87b62fe173437c9b15ba76ee3ad3059250100000016001422a8870cac68d8633dd1a3ba560c388df14be86dffffffff022c0f010000000000160014f0fa7ce0b3d892e2e873e92103c7e01605e3a1af6c7404000000000016001422a8870cac68d8633dd1a3ba560c388df14be86d02000000000000"
},
"id": 0,
"jsonrpc": "2.0"
}
When done directly to the node. (But have to check why is not working on the website…) -
May be related to v10. My understanding is that 1 or more of the api.counterparty nodes have been updated.
There will an another v10.1 release very soon.
https://github.com/CounterpartyXCP/counterparty-core/pull/1640
Hopefully this solves most/all issues, but it is still a release with MANY changes, so the safest is to rely on v9.61 for critical infrastructure.v10.1.0-rc.1 by ouziel-slama · Pull Request #1640 · CounterpartyXCP/counterparty-coreRelease Notes - Counterparty Core v10.1.0-rc.1 Note: This update requires a reparse from block 835,500. (If you are upgrading from v9.x.y, then you need a full database rebuild.) ChangeLog Bugfixes...
-
And the website is fixed now
- 13 April 2024 (25 messages)
-
@Jpcryptos you were working on a counterparty rust lib right?
-
Just curious how it was going, you still working on it?
-
Straight v9.61 db without any new indexes? v10 fixed a bunch that used to have conflicting names
-
Casey (@rodarmor) on X
Light Pools: A simple solution for decentralized trading of Bitcoin-native assets. Mempool-sniping resistant, price and cost effective. I'm not going to build this one, unlike runes where I was like, eh, who knows. I hope someone else does! 🧵 https://t.co/euLTnYIckk
-
This could easily integrate with utxo bound counterparty assets if someone builds it
-
P2P is hard imo
-
agree, i dont think its "better" than AMMs persay but still interesting and someone will probly try to build it
-
AMMs are buyer, seller and market maker
-
I can send you some in a few hours if no one else has any
-
I would love to stop by! (As a visitor, don't have much to say 😁) -
When will it be? Sounds interesting
-
Yeah you got a link with more details?
- 14 April 2024 (4 messages)
-
- 15 April 2024 (9 messages)
-
Haven’t used testnet in a while 😆
-
People prepping for runes launch
-
There’s also some runes projects that are rewarding “points” for testnet mints
- 16 April 2024 (22 messages)
-
I’m using the docker compose installation. Did a git pull.
Next trying this command:
docker-compose up -d --force-recreate counterparty-core
But is not working, getting this error:
ERROR: Configuration for volume data specifies "device" driver_opt /root/counterparty-core/${XDG_DATA_HOME:-~/.local/share}/counterparty-docker-data, but a volume with the same name uses a different "device" driver_opt (/root/counterparty-docker-data). If you wish to use the new configuration, please remove the existing volume "counterparty-core_data" first:
$ docker volume rm counterparty-core_data
It says the solution is to delete the data folder… which I could do (because I’m still testing everything relying on bootstrap) but just asking here before in case the delete is not necessary. -
Thanks. But still getting the same error…
-
FYI used this (fixed typo):
export COUNTERPARTY_DOCKER_DATA=/root -
With success or having the same issue?
-
And btw, was starting the delete data folder path, but it seems all containers (including the bitcoin one) are tied to it… so will deleting it mean that I would have to sync Bitcoin again?
-
Ok then, good to know.
Guess is a good moment to also announce that I was removed as a member of the “official” repo in the weekend. Is only Adam now it seems… -
Deleted everything and now I’m getting this:
https://github.com/CounterpartyXCP/counterparty-core/issues/1690Docker compose installation failing · Issue #1690 · CounterpartyXCP/counterparty-coreSteps To Reproduce Following the instructions from https://docs.counterparty.io/docs/basics/getting-started/. git clone git@github.com:CounterpartyXCP/counterparty-core.git cd counterparty-core mkd...
-
Time
-
Be that as it may, this chat has the most honest, upstanding and active members with good intentions. The other dev chat is more of a level 1 tech support at the moment.
-
And the number of members has never being an important metric here. Maybe the opposite.
The bio explains the purpose of this group. Then add the Decentralizing CNTRPRTY project (github.com/CNTRPRTY), which this would be the “support chat” for.Bitcoin and Counterparty ToolsDecentralizing CNTRPRTY: "Counterparty is Bitcoin. Is on top of Bitcoin. Is Web3. Is Web5. Two steps ahead." 🐸 - Bitcoin and Counterparty Tools
-
😂
- 17 April 2024 (24 messages)
-
http://v10.0.0-rc.1.preview.xcp.dev.s3-website-us-east-1.amazonaws.com is back up. It is still running v10.0 which is out of consensus because of 1+ bugs, but it will be updated to v10.1 as soon as the docker installation is fixed.
But I still encourage everyone to see it and compare it to (still v9) xcp.dev. There are a couple of key differences, noticeable in the unconfirmed transactions in the homepage and block/<block> pages.
v9 and v10 are both following the same protocol. Then, the consensus hashes are matching 2 of the 3 values. The one mismatching is the messages hash. And as seen in v10 xcpdev, the messages in v10 are now representing “events”. -
Has anyone been able to successfully multisend recently
-
I'm getting AddrIndexRsClient -- Error in response: timed out
-
I was using Free Wallet, so it could be that, but it's aimed at api.counterparty.io
-
I reinstalled FreeWallet and it worked, so maybe there was a minor point version JDog pushed or that helped clear out some cache.
-
False alarm
-
i have detected some issues after update to 10.1.0
-
my node has stopped parsing blocks at 839627 without any error message or warning despite i have it in verbose mode
-
addrindexrs and bitcoin are synced with the tip but not counterparty
-
i had to kill the process and start the container again, i will monitor to see if this error happends again and report it propperly, want to discard it was an isolated error of my setup
-
What installation method?
-
Docker
-
But without docker compose
-
Now looks good after killing it
-
Whatever you can share of the procedure you followed…
-
I just stopped counterparty container and changed the version of the image used to counterparty/counterparty:10.1.0 and docker run
-
I had to export the env vars again
-
# COUNTERPARTY INSTALLATION STEPS USING DOCKER (TESTED):
- 1. Create Persistent docker Volume:
- docker volume create -d local -o type=none -o o=bind -o device=/root/.bitcoin/ data
- 2. Run bitcoind and wait until sync:
- docker run --rm -d \
--name bitcoind \
-v /home/.local/share/counterparty-docker-data/:/bitcoin/.bitcoin \
-p 8332:8332 \
kylemanna/bitcoind:latest -chain=main -rpcallowip=0.0.0.0/0 -rpcbind=0.0.0.0 -rpcuser=rpc -rpcpassword=rpc -listen=1 -server=1 -printtoconsole=1 -addresstype=legacy -txindex=1 -prune=0
-dbcache=4000 -mempoolfullrbf=1
- 3. Export env var for bitcoind:
- export DAEMON_RPC_HOST=$(docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' bitcoind)
- 4. Run Addrindexrs and wait until sync:
- docker run --rm -d \
--name addrindexrs \
-v /home/.local/share/counterparty-docker-data:/root/.bitcoin \
-v /home/.local/share/counterparty-docker-data:/data \
-p 8432:8432 \
counterparty/addrindexrs:v0.4.6 \
--network=main --indexer-rpc-host=0.0.0.0 --daemon-rpc-host=$DAEMON_RPC_HOST --daemon-rpc-port=8332 \
--cookie=rpc:rpc -vvv --db-dir=/data/
- 5. Export env var for addrindexrs:
- export ADDRINDEXRS_HOST=$(docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' addrindexrs)
- 6. STOP bitcoind:
- docker stop bitcoind
- 7. Run Counterparty on kickstart mode
- docker run -it --ipc=host \
--volume /home/.local/share/counterparty-docker-data/:/root/.bitcoin \
--volume /home/.local/share/counterparty-docker-data/:/data \
-p 4000:4000 \
-e XDG_DATA_HOME=/data/ \ -e XDG_LOG_HOME=/data/ \
counterparty/counterparty:v10.0.1 \
kickstart \
--mainnet \
--backend-connect=$DAEMON_RPC_HOST \
--indexd-connect=$ADDRINDEXRS_HOST \
--rpc-host=0.0.0.0 \
--bitcoind-dir=/root/.bitcoin/ \
--verbose \
--force
8. Once synced with kickstart, pause counterparty and remove it.
- docker stop counterparty && docker rm counterparty
9. Start again bitcoind with the same command showed in point 2.
10.Update counterparty to v10.1.0 and run it with start instead of kickstart
- docker run -it --ipc=host --name counterparty \
--volume /home/.local/share/counterparty-docker-data/:/root/.bitcoin \
--volume /home/.local/share/counterparty-docker-data/:/data \
-p 4000:4000 \
-e XDG_DATA_HOME=/data/ \
-e XDG_LOG_HOME=/data/ \
counterparty/counterparty:v10.1.0 \
start \
--mainnet \
--backend-connect=$DAEMON_RPC_HOST \
--indexd-connect=$ADDRINDEXRS_HOST \
--rpc-host=0.0.0.0 \
--verbose \
--skip-db-check
WARN: --verbose and --skip-db-check flag are optional, I added --skip-db-check after experiment some issues in this step. -
Maybe this is useful for someone :)
-
xcp.dev has been updated, focusing on the wallet’s create section!
Methods available:
create_broadcast
create_issuance
create_send
create_dispenser
create_order
create_sweep
And (some) advanced parameters are available for all. For example, manually choosing the encoding for the transaction! - 18 April 2024 (2 messages)
-
@herpenstein gm, I have been reading through 721 protocol specs (great stuff) and I have a few questions if you find the time to share.
Does 721 still share the stamps indexer and is there an opensource indexer for others to run locally for 721 or stamps? Great idea implementing cp asset ID.
I’m overthinking the reveal, is there more info on revealing/compositing the layers for the user?
Could person A create a ‘Single Item’ (not in a collection) token with some traits from collection B, one trait from person C’s asset, and a trait from asset D?
How much magic is the indexer doing in 721 world? What are your thoughts about using 721 specs minus a collection?
Amazing contribution, wonderful documentation. Is your github still the best place for 721 details? Please let me know if there is a better dev chat for 721. Thanks. -
Just updated to include all advanced parameters. And added a couple of more methods.
Done with the wallet for now, unless I receive specific feedback - 19 April 2024 (4 messages)
-
I have a stamps question. Looking at their chat I see clams about “mutability” when comparing it to other projects like runes…
What can be mutable in Bitcoin? Isn’t that the whole point of the block hash?
Maybe the confusion is with the “prunable” data, which is after the fact, and optional for the nodes that which to not store the complete history…
Or maybe I’m deeply confused 😆 -
Yeah I’ve mistakenly used mutability in place of prunability sometimes. Ignore that. -
Ok then. Asking because is not the first time. Or the messages get re-quoted
- 21 April 2024 (7 messages)
-
Interesting that kickstart begins from the latest block and goes backwards, instead of the natural increasing order of blocks…
-
Then it goes back up, and takes less than 0.1s per block for most in my machine. And gives an estimated completion time, which is less than 6hrs for me.
Pretty cool, first time running it this way -
Now it says 10 hrs, still better than… weeks 😆
- 22 April 2024 (6 messages)
-
Now it just says “1 day”, which is not very useful in this context, maybe is better to just keep the hours. Is at block 671000…
-
Same ram, but is ec2 ‘s “t2.large”. Which is 2 cores
- 23 April 2024 (3 messages)
-
New v10 preview website, running the latest v10.1.1:
http://v10.preview.xcp.dev.s3-website-us-east-1.amazonaws.com/
(PS: My bad about previous message, it was only working for my ip 🤓) -
thought I would ask here, does anyone have some extra signet btc they can send me for testing?
- 24 April 2024 (61 messages)
-
Has 'get_tx_info' been removed from the API? -
ty
-
I am getting a 500 error from public.coindaddy.io when I try get try a get tx info
XCP Dev Chat
Public archive of Telegram messages.
- 01 Apr 2024 (59)
- 02 Apr 2024 (53)
- 03 Apr 2024 (69)
- 04 Apr 2024 (28)
- 05 Apr 2024 (9)
- 06 Apr 2024 (3)
- 08 Apr 2024 (22)
- 09 Apr 2024 (45)
- 10 Apr 2024 (56)
- 11 Apr 2024 (12)
- 12 Apr 2024 (31)
- 13 Apr 2024 (25)
- 14 Apr 2024 (4)
- 15 Apr 2024 (9)
- 16 Apr 2024 (22)
- 17 Apr 2024 (24)
- 18 Apr 2024 (2)
- 19 Apr 2024 (4)
- 21 Apr 2024 (7)
- 22 Apr 2024 (6)
- 23 Apr 2024 (3)
- 24 Apr 2024 (61)
- 25 Apr 2024 (1)
- 26 Apr 2024 (10)
- 27 Apr 2024 (1)
- 29 Apr 2024 (9)
- 30 Apr 2024 (7)