so for future reference, these DBs compress very well

with gzip a full DB goes from 9GB to 2GB; with xz it goes down to around 1GB (depending on compression level)

it's great in general but they don't joke around about metering

It’s metered?

yep

What is the caps? I just ordered yesterday and didn’t even see that

no hard caps they just provide slower service after 1tb of monthly data i believe

Ugh

you can upgrade your service but seems that you need to upgrade your satellite along with it

the data is unlimited but your bandwidth gets capped after a certain amount of data transfer

I found it comparable to DSL when I went over.

I’m on a 40/10 connection and suffering so I thought this would fix, but if I get throttled it sounds like it will be the same thing

oh yeah starlink is in any case not better than cable

it is better than dsl, as good as cable (if you aren't being metered), and worse than fiber.

I was on 10/1 so it was life-changing for me

I don't do anything too fancy so only time I ever hit the high speed usage cap was syncing a bitcoin node lol

I do not think that I have been metered yet. We watch all our HD tv thru it. It was fully unlimited then they put fair use on it. The metering is for the remainder of the month. It has been rock solid for me

@robotlovecoffee I think the link you provided may have expired.

ya I can only share it for 12 hrs

https://mmord.s3.us-east-1.amazonaws.com/counterparty.db?response-content-disposition=inline&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEA4aCXVzLWVhc3QtMSJHMEUCIAWh1FGhi30fxMBM32jkV3plq6VxovPOlK3mzltoNyb2AiEA63SDiU5KpHi8iDlQ%2B4NoXOeBMFvheQBEov92lzz%2B8lgq6AIIFxAAGgw2MDYyOTE0Nzc3MjkiDG9rE2VtHxZHvx2UIyrFAullokmnh%2B%2BMdI%2FqLR6gHY46Z7zTTw8xApzQPzyiBx93hAFRdPMUBEzeohNVwsaU%2BECfa1jDJPTt%2FPVntbsoaSRUSmoIHK9LrKcPtW1TfYiKbAo5NvWIvcWckO8PK4LKfF%2Bv6sYTOR3%2BnZ8qGy1wSlJ7FET09Ibbten4B38xXc%2BFQ0pd6KmUR09ihZn5RGYR8c78%2FjkEbQf6UbZ2ZGEfUW7HJ56TPWXXRJlS%2BuptTwYNqA7%2BqecITV7iVkfpnZlviDqyCXuDcwfzrIgtbfWL4P0BhD390e5v%2F1V88bCKH8mWEWr%2Bmx8Q7qQyTo7CG8wJThw1VrGuoDVBX6DTVgXrW6lbDaSidA%2BWsdcgEYNRx8ElAWdxoZCLxWy%2Br%2F4bJzEUGiNv9AvJWIxgg%2FZhK4yUBwMhYaZXYD9ZY0%2Bm9OGJCumTWK0Mjlowv%2Bq2rwY6swJjLGRjruGSQpctMo4a2CIysTB57gx9pncOtc5ZGwiRZdF1S0u%2F2UuP8vtdJl06xMpPOygAeLRRI0xd6IdDiyyBzHzOA%2B6xcPP38S5CzS4y2o4UyRp1s73QH3DwuY6B5U6Pp7ltcHmrOR2Zis8wC3w3ArCRpDoG6ClkiesD2D1oASDrKSkG7kHVBDetDuyzp%2BG12HjqFCsAPmNCj47pm2NbNuXPxjt4UP3%2F3DR70MPsLUxGeR7tjNssh62GujfQXh50WOfkEbEarBhd6iTpiZtQQGBDu4H2aSYBdhnaXTqYtOp5qXDsmaIXINNZAlyh95tK5%2Bg4698yrzcVqPavEhpy45FiLIH8xk5YpafPBRAJ9mWyv0oROBtstp3wmT2NiuJFMhVr3XXBz8D%2BeNc7wK49QXzH&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20240310T132802Z&X-Amz-SignedHeaders=host&X-Amz-Expires=43200&X-Amz-Credential=ASIAY2KOJYTQWCHG4G6C%2F20240310%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Signature=40a83df477a395caf938643ca1cbefbcda3fc5025457a758662996e876ee68ef

@robotlovecoffee same issue as last time: your node is not seeing a simple send...

this isn't a non-determinism so not sure what is happening!

has anyone else running develop hit a consensus hash mismatch?

I think that I should nuke this instance and start fresh

@robotlovecoffee before you do that, could you give us access to the instance to debug it directly?

a consensus break like this is something that should *never* happen; if it does, there's almost certainly a bug we need to fix

and we haven't been able to figure out what the problem is from the database file

Sure not in shop at the moment. If I get you IPs I can add you ssh access. Can we do that tomorrow?

I get a sense that my setup is botched a bit but having you guys verify would be helpful

Ouziel found the problem. Catching a generic exception was hiding an incompatibility in the implementation of ripemd in a dependency

thanks again for the help debugging! 🙏

awesome

checkpoints passed. will lyk if we hit any further issues.

great news ser

dex live on rarepepewallet.wtf

Huge

Anyone have the counterparty dev fund multisig address and that pdf announcement they put out last month?

Sorry yes, still working on porting over the blog posts to the new website

Thank you ser

Are you guys are still accepting funds on this wallet?

3G2bY5De2sbWT5iE4KBKXCSRKbEu8n6RCc

I'm trying to migrate from using xchain call as getting blocked or rate limted all the time but running into issue using the CP API. I want to get a list of dispensers for an asset. But having an issue just get_asset_info. I have other calls working so not sure if this API is not working. I was going to hit the tables direct with the get_{table} but not sure where to find db schema.

Just do a generic get_ call with no parameters and use the results to see what you can filter by

thks, sometime the answer is so simple...

hey! if anyone's going to be at the NFT.NYC 2024 conference in April, I'll be there IRL and would love to meet up :)

will try ser would love to meet you

Hi everyone! Super excited to announce the alpha release of counterparty-core v10.0.0: https://github.com/CounterpartyXCP/counterparty-core/releases/tag/v10.0.0-alpha

A huge thank you to everyone who contributed, especially Ouziel Slama, who put forth a heroic effort to get this done!

Good catch! thank you so much @ChiefSamyaza

I'm trying to create a token in a wallet that has a known private key and sweeper bot. I was hoping I'd be able to take advantage of the mempool fees, but freewallet is not pushing the transaction through due to insufficient funds. I'm trying to create the unsigned tx using xcp.dev now, but I'm getting an error

Can someone help me figure this out?

Here's what inspired me to try this: https://www.sothebys.com/en/buy/auction/2024/r-evolutionaries-digital-art-through-the-decade/torched-h34r7s-1flamen6

One of the most legendary pieces of Bitcoin art, and they chose to use superrare's contract to issue a token. I thought it'd be cool to issue TORCHED.H34R7S from the 1FLAMEN6 address.

https://mempool.space/address/1FLAMEN6rq2BqMnkUmsJBqCGWdwgVKcegd

look at those release notes! amazing work

Study Counterparty

Pub Key Bar

what would be the best steps for my AWS instance to get on new release?

should I nuke all and start fresh as a test?

you don't have to nuke everything! you should update to the latest addrindexrs and counterparty-core

you will have to rebuild your Counterparty DB because of a version number bump, however, so run counterpary-server kickstart again

I was just nervous as I might have not setup very clean when I 1st did it, but will look to just get the latest

off topic does anyone know the path to get all dispensers for an Asset without using the xchain API, I do not see an easy path via the current API but might be missing something?

Pretty sure theres a get_dispensers call, not at my computer to check

Then just filter by asset and status

What are the storage space requirements now with bitcoind and counterparty v10 on the same node?

still same as before. about 1.1TB for mainnet

So right now you can either use`kickstart` if you run directly on the host, which is fast. Or you an run simplenode using start, which is slow (but will get faster!). simplenode will support bootstrap before v10 is released, but if folks can run kickstart for the alpha release it'd be really helpful!

that needs a hash or TX so I think I need to parse and store data to get a list which I was hoping I would not need to do

Finally, xcp.dev has a formal public api. It is basically the same api the website uses.

Starting with a subset of all endpoints (and with a very basic doc page 🤓).

https://www.xcp.dev/api

Many people have asked for this, and seeing some recent questions here. Hopefully this is just a first step to continue improving it and maybe even offer a premium paid alternative eventually.

But it is all free for now. And because it is “formalized” the endpoints and responses (posted in the doc page) should not change. But this is not a guarantee and I will at least announce here any breaking changes.

Feel free to post feedback in the repo, here or DM me directly. And let me know any endpoint you would like to be added next.

We’re doing a Counterparty space Wednesday to discuss v10.0.0 set your reminders ✅ https://x.com/emblemvault/status/1769815353482154225?s=46&t=VKlzOqs5vqDWcDUEI3d16wW

Already running it, with the simplenode approach

Were you able to solve this? With the recent (today) update to the api the Create tx part is not working. But you can DM me if you still need it and I can work on it

Thanks, I'll circle back to that soon and DM you then. Joe didn't think it'd be possible to beat the bots, but I feel like it can be done given the mempool conditions.

awesome. did you run into any bugs?

Bitcoin syncing still. I am running it in a server so I had to stop the containers and then restart the Bitcoin one specifically. Should be done syncing by tomorrow and then I’ll proceed to addressindrs…

Using an ec2 large (8GB ram) with 1 TB. The same specs as another v9.61 node I have to be able to make tests and comparisons.

spinning up a new simple node

let see how it works

i found a really good deal

https://www.piensasolutions.com/dedicados

25€/month 64GB Ram and 2x2TB hdd

Testing it now will let you know how it works

At the moment syncing bitcoind at light speed

got a weird issue with a dispenser tx not showing up in counterparty block explorers... filed it as an issue - will post more info to the issue when I get more info from the user on how to recreate it more specifically:

https://github.com/CounterpartyXCP/counterparty-core/issues/1534

this may be the txid thing

I believe this is mostly addressed with 10.0 but to address it fully I think we need to get rid of addrindexrs

Have not been able to get addressindxrs to work…

First got these 2 errors:

Error: An unknown argument '--indexer-rpc-host=0.0.0.0' was specified.

Error: An unknown argument '--daemon-rpc-host=0.0.0.0' was specified.

Both which I commented out to get the container to stay up. But now I see:

WARN - failed to connect daemon at 127.0.0.1:8332: Connection refused (os error 111)

Mine is still syncing bitcoind

Cool then you’ll get here very soon…

Okey cool

@uanbtc are you using addrindexrs v0.4.3?

adam@api4:~$ ~/addrindexrs/target/release/addrindexrs --indexer-rpc-host=foobar
Error: Failed to parse argument '--indexer-rpc-host': invalid IPv4 address syntax.

Hint: the value must be a version 4 IP address.
adam@api4:~$

works for me on multiple machines

WARN - failed to connect daemon at 0.0.0.0:8332: Connection refused (os error 111)

same error here

How? -version and alternatives don’t work…

Last commit Jan 29

I see the docker image was updated yesterday

ah yep that's an old version

if you're using docker, use the new image

what is the new image?

just realized i was on master

you can just do docker pull counterparty/addrindexrs

the new addrindexrs is (now) on master

yes but i mean i was on counterparty-core master

ah

I mean counterparty-core on master is at v10.0.0-alpha

Same here now, with 0.0.0.0

WARN - failed to connect daemon at 0.0.0.0:8332: Connection refused (os error 111)

I fucked it lol syncing again bitcoind

Jejeje

After doing this

ach yeah I can't wait till we can kill addrindexrs

the "daemon" is bitcoind I think? so it should be 127.0.0.1

the naming is bad ofc

WARN - failed to connect daemon at 127.0.0.1:8332: Connection refused (os error 111)

Mmmm as you are connecting it inside docker

Maybe is nos 127.0.0.1

Mmmm Will need to do further checks, tomorrow will do some tests

Same here

https://github.com/CounterpartyXCP/counterparty-core/issues/1536

Is not bitcoind-dir param available for counterparty-server on docker?

Because I think I solved this IP issue but I receive an error to use --bitcoind-dir param but when I add it to the list of commands in compose throws the usage error with this :
counterparty-server: error: unrecognized arguments: --bitcoind-dir=
/data/bitcoin

Sorry I don't have the previous error where it says to introduce the bitcoind-dir argument

I'm modifying the compose.yml in my own to make it work will share when I have it

I'm trying to do it with kickstart I'm pretty sure that just changing the IP to your own works in start, I need to try with machine hostname as should work too

@XJA77 bitcoind-dir argument works for me.

~/c/c/counterparty-lib (master)> counterparty-server kickstart --bitcoind-dir ~/.bitcoin/
Running v10.0.0-alpha of Counterparty Core.
Writing log to file: `/home//.cache/counterparty/log/server.log`
------------------------------ kickstart ------------------------------

Mmmm mayby i need to use the .bitcoin

Maybe I'm using wrong the argument

are you sure you're putting it after kickstart, not before?

Nope o was putting it before

That's the issue then

👍awesome

Will check it

Linux aliases make life easier

@Jpcryptos ouziel just pushed a fix to develop, please lmk whether it's solved for you!

adding it after i get this error:
[2024-03-20 15:03:46][INFO] Running v9.61.1 of counterparty-lib.
[2024-03-20 15:03:46][INFO] Acquiring lock.
[2024-03-20 15:03:46][INFO] Connecting to database (SQLite 3.24.0-r1).
[2024-03-20 15:03:46][WARNING] Warning:
- Ensure that bitcoind is stopped.
- You must reindex bitcoind after the initialization is complete (restart with `-reindex=1`)
- The initialization may take a while.
[2024-03-20 15:03:46][ERROR] Unhandled Exception
Traceback (most recent call last):
File "/root/miniconda3/envs/xcp/bin/counterparty-server", line 33, in <module>
sys.exit(load_entry_point('counterparty-cli==1.1.5', 'console_scripts', 'counterparty-server')())
File "/root/miniconda3/envs/xcp/lib/python3.6/site-packages/counterpartycli/__init__.py", line 16, in server_main
server.main()
File "/root/miniconda3/envs/xcp/lib/python3.6/site-packages/counterpartycli/server.py", line 169, in main
server.kickstart(db, bitcoind_dir=args.bitcoind_dir)
File "/root/miniconda3/envs/xcp/lib/python3.6/site-packages/counterparty_lib-9.61.1-py3.6.egg/counterpartylib/server.py", line 503, in kickstart
blocks.kickstart(db, bitcoind_dir=bitcoind_dir)
File "/root/miniconda3/envs/xcp/lib/python3.6/site-packages/counterparty_lib-9.61.1-py3.6.egg/counterpartylib/lib/blocks.py", line 1232, in kickstart
if input('Proceed with the initialization? (y/N) : ') != 'y':
EOFError: EOF when reading a line
Proceed with the initialization? (y/N)

looks like require some user interaction?

lol that's a new Traceback...

no way to bypass it? tried with —y but no

but in order to start you don't have to say 'y'

checking...

is kickstart

you're saying that if you let it proceed it fails?

the traceback is ugly but not sure I understand what's blocking you

is inside a docker so i dont have this access

i can do it interactive

but is not ideal

ah that's a good point!

okay that sounds fixable.

cannot run it in interactive to accept

yep, we should just add a -y flag

thanks for bringing that up @XJA77 !

@XJA77 TIL you can use --force to make it non-interactive

so you should be good tog o.

so just —force

will check

yep, not sure if it needs to go before or after. lmk!

no works neither

is before

but no works same traceback

Live. Raise your hand if you want to speak https://x.com/emblemvault/status/1770473049692971454?s=46&t=VKlzOqs5vqDWcDUEI3d16w

@teysol is in

@teysol listening to the space, if you see this and want to talk about it, would you please talk about the patents? The process, details, thoughts, reasoning etc.

FYI for anyone who wants to send Ouziel (who's been working like a madman) a tip, he has a donation address in his GH profile: https://github.com/ouziel-slama

what patents?

okay this was a bug specifically with the Docker deployment! Ouziel just fixed it, but the fix also requires a new addrindexrs Docker image. he's releasing that now

should i be using development branch then? or master should work?

I think we're gonna make a beta release including this fix (and others)

I’ll be waiting for the release before trying again

Me too

v10.0.0-beta.1 is out (https://github.com/CounterpartyXCP/counterparty-core/releases/tag/v10.0.0-beta.1)

Changes from v10.0.0-alpha:
* Run automatic software version every 24h rather than on every block (with dither)
* Add the possibility to reparse from a given block on minor version change
* Add warning with confirmation dialogue to bootstrap command and --no-confirm flag
* Add checkpoints for mainnet up to block 834,500 and for testnet up to block 2,580,000
* Re-enable additional tests (testnet "test book") in CI
* Automate Docker image build and publish
* Increase AddrIndexRs required version to v0.4.4
* Accept config args both before and after the command
* Fixed a bug in v10.0.0-alpha that broke Docker Compose deployments (e.g. with SimpleNode)

Only 3 open issues remaining (of 106!) before we get a v10.0.0 release candidate. (https://github.com/CounterpartyXCP/counterparty-core/milestone/12)

awesome just one thing

we need to version the dockerfile

So when there is a new change, the docker image is rebuilt with the new changes

@Jpcryptos what do you mean?

when you do a git pull from the repo and.

docker-compose -f simplenode/compose.yml up

docker just execute
https://github.com/CounterpartyXCP/counterparty-core/blob/master/simplenode/compose.yml

but the version is still 3, So if you have the image already installed docker does not rebuild it... so if there has been a change in any repo parent, it may not be reflected. it happened to me and I had to do docker prune to delete all the images and rebuild again.

A worked this time perfect.

but I don't know if changing the version will remove the volumes, and also the bitcoin node synchronization will be lost.

I'm using the --build flag

But I think still not pulls the docker images

Maybe adding version explicit in the docker images

Change the version to 3.1 and try it.

another question, what is a good reference now to check consensus hashes?
im getting this: Block: 304812 (0.19, hashes: L:bf519 / TX:02701 / M:664d1) but xcp dev showing this

Version 3 refers to the version of the Docker Compose syntax, I think...

FWIW I’m team anti-docker. Carry on.

this is my understanding too, but i think that explicit versions of the image solves this

hm I think you're right @XJA77

https://stackoverflow.com/questions/37685581/how-to-get-docker-compose-to-use-the-latest-image-from-repository

we should update the docs to include docker-compose pull

also maybe in docs add the -d flag in the up command is good

-d is just for --detach I think

Yes is for detach

I prefere normally do it detached and then run
docker compose logs --follow

I’m now getting:

Error: Failed to parse argument '--daemon-rpc-host': invalid IPv4 address syntax.

Hint: the value must be a version 4 IP address.

ach hm this is with the Docker Compose?

we still don't have that in CI :/

I solved it

Needs the IP of your machine

Set inside the docker compose?

--daemon-rpc-host=<my-ip>

Yea

Instead of bitcoind

The container now stays up, but still not connecting. Anyway it should be connecting through the ‘bitcoind’ host so something seems to still be broken… or I’m doing something wrong

yeah so Docker uses hostnames to link multiple containers together

looks like the type-checking in AddrIndexRs doesn't like that—it's expecting an IPv4 address

looking into it 👌

(and tests that are being written right now will catch this kind of problem in the future) cf. https://github.com/CounterpartyXCP/counterparty-core/issues/1533

Same... after 0.4% bitcoin sync

yep, it's a bug in the Docker deployment :/ should have it fixed by EOD tomorrow / early Saturday

@uanbtc @Jpcryptos what version of addrindexrs are you running? did you do docker-compose pull after upgrading?

Im looking through the api trying to figure out the entire dex flow.

I see how to create an order and how to cancel an order, but how do i execute an open order? Do I create another order with the opposite give/get?

I feel like I’m missing something very simple

yep you just create another order that will satisfy an existing one

the order matching itself happens in the protocol

Kk thanks. Appreciate it

Spent 10 minutes trying to find « execute » or something similar

This did it! Indexing now, thank you

@herpenstein this happens in the order_matches table. You can see how xcpdev uses it:

https://github.com/CNTRPRTY/xcpdev-genesis/blob/d5bf3676f196e557fa006c3d2aec3795de828af8/server/express_server/src/index.js#L394

Yeah because this command becomes necessary any time the docker images get updated, right?

actually we changed it to have the docker image versions pegged in the compose file so now that's not necessary

Thank you ser, appreciate it. I was derping pretty hard this afternoon

rather than escrowing tokens to utxos for use in psbts when utxos can then be spent without moving the token causing the need for 'lost token' recovery mechanism, a preferable method may be to use chamian ecash tokens rather than utxos

Utxos will need to be tracked during the binding process so spending them should simply result in an asset send, so I don’t see why there would be any type of ‘lost token’ recovery mechanism

when encodign the enchance_send , should the utxo input for rc4 be the txid of the previous enchance send ? or should it be the txid of the op return transaction ?

should .. yes .. but what happens when a utxo is spent but the token is not sent? e.g. private key used in a wallet that is unaware of Counterparty, the token is tied to a utxo that then no longer exists ? unless of course part of the binding spec is for token to be returned from escrow in the event the utxo is spent and the token is not sent

The token is sent regardless

It’s no different than colored coins in that respect, if you accidentally spend the utxo then you accidentally send the token

that makes the most sense, hopefully the utxos are spent to counterparty compatible addresses and in time counterparty supports all addresses.

Would the psbt tied to UTXO model allow double spend? Pre sign one tx and spend the UtXO with another tx. Unless multiple transactions are stacked and using BTC script wisely.

That’s not a double spend

Starting counterparty sync now…

super excited to hear how it goes, Juan!

Yea me too. Starting well many blocks less than 0.05s

I didn’t know what else to call it but yeah. I guess it doesn’t matter.

hello, still syncing, but im getting some missmatches in the messages hash
717190 (3.33, hashes: L:bb9dc / TX:b160e / M:864c4)

anyway looks much more faster than before, im using no bootstrap to catch up and in 4 days im at block 717kish

so messages hash is not a consensus thing. not sure if this should be filed @teysol

I am glad even start is faster! kickstart is pretty reliably less than a day.

FYI getting these after 819300: https://github.com/CounterpartyXCP/counterparty-core/issues/1553

appears to be an addrindexrs non-determinism :/.

imposible to make it work on docker despite i tried :(

but yea looks much faster now :D

I believe kickstart will be mooted with v11 anyway! so start will be fast, too.

It's a belt-and-suspenders thing.

what mismatches are you getting?

Mismatches in messages hash

yeah, please post screenshots and logs (to GitHub)

Not at home so will be hard during some days

Just connected to check progress through ssh at mobile

Are subassets tradeable?

Yes

cool, ty!

I’m at 481500, almost 3 days after so not as fast. But I’m using a lower spec machine than you I think.

The messages are mismatching from the beginning. There are schema changes in tables like credits and debits that are used from the start…

@uanbtc you're using start yeah?

If that is what is used in straight simplenode, then yes

got it. yeah, that'll be fast with v11, when addrindexrs is killed

Has worked for you the start with bootstrap?

For me was supposed to be with bootstrap but started no bootstrap

I haven’t modified anything. I hope I’m not using the bootstrap… I think the new default is without bootstrap? @teysol Periwig

@uanbtc what are your specs?

the new default is definitely without bootstrap

Ec2.large. 8GB ram and 1TB ssd

Is the cpu the bottleneck?

I run everything on a 2-core machine

@XJA77 what’s your machine specs?

Yes. Not using the full ram but yes 100% of cpu

How much ram are you using?

my ram usage has been de minimis

Sorry for the 50 questions. Trying to figure out my future setup

i've got super boring specs: 5 core i7 8gb ram 24gb swap. ram is really unaffected

some of my cpus definitely are just chilling while I run kickstart

hardware reqs are really quite light. @teysol's sync speed with 3x mine with his M2 though

I've specced with 12GB of RAM

Im considering throwing up one of the smaller ec2 instances to see what the lower limit is

Otherwise I think I have a 2gb pi somewhere

yeah it'll also change a bit once we get rid of addrindexrs

and we haven't done any profiling of counterparty server memory usage

it's also managable with these ugly CLI args like --max-queue-size etc.

2GB still available of the 8

I have this one the big one and works perfect and cheap

Yeah is crazy how cheap it is! I might try it eventually

Works good

Not as automatic as aws stuff but...

Hey guys, is there a way to use xcp.dev with the dex?

What do you mean specifically? Currently you can access all market data based on the asset page. And the address page shows dispensers also.

In the wallet, order transactions (and creating dispensers) are not yet available… but i could work on it…

FYI I’m currently battling manual install on newest Debian LTS.

I caught dependency problems with addrindexrs for cc complier and clang while installing addrindexrs but they didnt stop me. Slight hickup with librocksdb. I manually handled the dependencies and moved on to next step.

More install notes to follow. Any input welcome.

I would love to know the best, affordable specs for running a node as I will want to run on in the cloud and also will be looking to have a local running.

AWS is not cheap but easy to stand up, ideally I would just find a cheaper dedicated cloud server

I'm running it here and works good, also I have one setup in local with a Ryzen and 16gb ram 2tb ssd

And works good too

yeah the specs you need today will just be higher than in a month or two

Yeah order transactions as far as i know are so far limited to FreeWallet

I’ll have it in mind, good to know you are interested

What do you anticipate will require higher specs?

Yeah FreeWallets monopoly is pretty lame

Nothing against FreeWallet tho

(I see you @ChiefSamyaza)

Kek

I have a 34 core AMD 256gb ram and 3TB, full synced with boostrap

Lol do it without bootstrap, curious to see how long it takes in such a beast

I'm saying it'll be lower in the future

Oh right I misread, cool!

Where do I tell addrindexrs that my blocks are in a different directory vs the default config?

I received an error initially where adrs was looking for blocks in the wrong directory, I made a change to daemon-dir in addrindexrs.toml and now adrs is erroring out with ‘IO error while lock file .db/mainnet/LOCK Resource temporarily unavailable. Any thoughts? Wait until v11?

pass the --db-dir arg to addrindexrs

so addrindexrs -vvv --cookie=$RPCUSER:$RPCPASSWORD --db-dir=/path/to/db-dir

you can find $RPCUSER and $RPCPASSWORD in your bitcoin.conf

No instant error there.

Indexing blocks

there ya go

lmk if you hit any issues

Now wait 3 days?

hm

no

addrindexrs will take some number of hours to finish indexing

after that if you're running directly on the host (which I guess you are) you:
1. stop bitcoind
2. run counterparty-server kickstart
3. wait 8-24hrs

wanna reiterate that this non-determinism surfaces after block 819300

if you get a consensus hash mismatch:
1.rollback to the last checkpoint (there's one at least every thousand blocks after 819300)
2. start bitcoind again
3. run counterparty-server start

Is this an always thing or some times thing?

Let me know if you want help trying to find the root cause.

I’m all caught up except for git clone/install of counterparty. Is there a new release coming soon you want me to test? Master branch or develop? I can wait to install counterparty if it makes sense.

I’m going to take a snapshot and backup now anyways.

i think everyone who wants to help test should run the latest release. thank you!

>Is this an always thing or some times thing?

It's a non-determinism so it's a sometimes thing

it's entirely possible you won't run into the issue, but I hit it 4(?) times after 819300

sorry, the latest *tag*: https://github.com/CounterpartyXCP/counterparty-core/tags

For the releases notes/readme. Debian 12 Bookworm LTS required pipx to install maturin. Also required clang and a c compiler to install addrindexrs. Apt install build-essential helps with dependencies in debian.

Hi @ffmad !

Hey 👋

@uanbtc did your node sync?

No is still in the 500k

hm. how long has it been running?

4 days

hm same as @ffmad who said he was at block 717k this afternoon.

What specs?

yeah idk!

ah @XJA77 hbu?

I'm at 807kish

So much better lol

Addrindexrs - something went south overnight, not sure what.

Nodes back up, addrindexrs says no more blocks to index, starting full compaction.

How can I verify the state/status of addrindexrs before continuing? Would you like me to check anything for the good of the project?

Some docs say to start adrs with —jsonrpc-import and others omit this options. Why/when/whats the difference?

Thanks.

if it's starting compaction you'rec in the clear. takes hours though. there may be documentatiom bugs as I think Ouziel god rid of the need for those args. @teysol ?

Cool, no nondeterminism errors here. I am taking plenty of notes too, to help update docs later. My counterparty dev journey stalled two years ago due to the state of the protocol. Please share any good development related links or docs you have for counterparty. Or what links to NOT read.

I guess I will wait for addressindexrs to compact before continuing with counterparty core.

Whats the deal with the —jsonrpc option?

@teysol FWIW the install docs for addrindexrs say to ‘git clone’ a samourai wallet version but the counterparty core install
Docs recommend git cloning from the counterpartyxcp repo. I have not compared the versions but this may be a cause of some problems.

yeah the counterparty docs are canonical

I'm not sure what the correct answer is, re: --json-rpc. I *think* it's not important, but AddIndexRs is absolutely terrible in general and we're killing it ASAP.

Ok yeah my test instance is less than a 1/4 of this machine lol. So it can make sense is taking 4x longer 🤓

Very nice you are doing the manual approach. And that you are taking notes to improve the docs. I want to do it manually eventually

@teysol Periwig mine is always showing “Blockchain cache miss”, is this expected?

I mean

it happens to me but not sure it's like a really awesome thing lol

seems harmless. a lot of the logs are not great and sometimes really scary.

From what I’ve seen it happens with every block

ah that hasn't been my exp

yeah that means something isn't working correctly (and it'll be slower than otherwise)

Should I debug? Is code dependent on the machine (cores, memory)?

thanks but it's all code that's getting thrown away in a couple of weeks

I’m headed towards a kickstart. Any suggestions?

Nevermind, pip and pipx are not playing along with debian as far as installing counterparty. I know I’m doing it the hardest way but thats fine by me. Any ideas to pip install counterparty on Debian before I get lost in my own research?

Debian externally managed environments needs

pip3 install . —break-system-packages

to install counterparty.

Kickstart = wrong addrindexrs. Needs 0.4.4 but I have 0.4.6

Note for install read me, the counterparty .config conf files are not made until after you run counterparty for the first time. I was looking for them before starting.

Is this because of the replacement of addressindrs? Like the block parsing logic will be refactored to integrate addressindrs responsibilities?

I changed my counterpartylib/config.py to check for 0.4.6

Now different errors. I think I need to check the server.conf and client.conf for my setup

No errors with counterparty-server start but errors with kickstart.

yup

blue@blue:~/.config/counterparty$ counterparty-server kickstart
Running v10.0.0-beta.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...
Unhandled Exception
Traceback (most recent call last):
  File "/home/blue/.local/lib/python3.11/site-packages/counterpartylib/lib/kickstart/blocks_parser.py", line 31, in open_leveldb
    return plyvel.DB(db_dir, create_if_missing=False, compression=None)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "plyvel/_plyvel.pyx", line 247, in plyvel._plyvel.DB.__init__
  File "plyvel/_plyvel.pyx", line 88, in plyvel._plyvel.raise_for_status
plyvel._plyvel.IOError: b'IO error: lock /home/blue/.bitcoin/chainstate/LOCK: Resource temporarily unavailable'

During handling of the above exception, another exception occurred:

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 220, in main
    server.kickstart(
  File "/home/blue/.local/lib/python3.11/site-packages/counterpartylib/server.py", line 555, in kickstart
    kickstarter.run(
  File "/home/blue/.local/lib/python3.11/site-packages/counterpartylib/lib/kickstart/__init__.py", line 328, in run
    last_known_hash = get_last_known_block_hash(bitcoind_dir)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/blue/.local/lib/python3.11/site-packages/counterpartylib/lib/kickstart/__init__.py", line 146, in get_last_known_block_hash
    chain_parser = ChainstateParser(os.path.join(bitcoind_dir, 'chainstate'))
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/blue/.local/lib/python3.11/site-packages/counterpartylib/lib/kickstart/blocks_parser.py", line 334, in init
    self.ldb = open_leveldb(leveldb_dir)
               ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/blue/.local/lib/python3.11/site-packages/counterpartylib/lib/kickstart/blocks_parser.py", line 34, in open_leveldb
    raise Exception("Ensure that bitcoind is stopped.")
Exception: Ensure that bitcoind is stopped.
blue@blue:~/.config/counterparty$ counterparty-server start
[2024-03-28 15:32:34][INFO] Running v10.0.0-beta.1 of counterparty-lib.
[2024-03-28 15:32:34][INFO] Running v10.0.0-beta.1 of counterparty-server.
Running v10.0.0-beta.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
------------------------------ start ------------------------------

[2024-03-28 15:32:34][INFO] Connecting to address indexer.
^C[2024-03-28 15:33:34][INFO] Received SIGINT.
[2024-03-28 15:33:34][INFO] Stopping backend.
[2024-03-28 15:33:34][WARNING] Killing address indexer connection thread.
[2024-03-28 15:33:34][INFO] Shutting down.
blue@blue:~/.config/counterparty$

I DID force the install by changing the lib to look for addrindexrs 0.4.6. So there is that. And I have 0.4.6 too.

Manual install. Debian LTS.

So we're testing everything in CI on Ubuntu latest

it Should Work(TM) out of the box with pip envs

Ubuntu is built on Debian. Debian is stripped down Ununtu, to a degree.

Installed ebbs. Still no go but different errors.

Start is working. Kickstart is not.

100 blocks in 22 seconds

wait

what is the error with kickstart?

that's really important.

Similar to above but different lines of code

I cant scroll up to see

can you kill start and run kickstart and post the error?

Let me check the log first

Important for proper function or development/testing? Just curious because start seems to be working fine.

it's important because kickstart is not only an official way to sync counterparty but by far the fastest

a ton of work went into optimizing it

Sorry. Same errors as above. It’s just hard to read and compare from phone, th, terminal etc.

https://t.me/xcpdev/10237

did you kill bitcoind before running kickstart

Yes

My blocks are stored in a nonstandard directory fwiw

did you pass --bitcoind-dir?

to kickstart

Ok I lied

Bitcoind was running once, but still erroring when bitcoind stopped.

yep

bitcoind shutdown can be really slow and annoying

Forgot I rebooted once.

Short version is TypeError ’NoneType’ object is not subscriptable.

sorry, from what command?

Need the full traceback in order to debug

Kickstart

I know. One minute. Multiple layers of systems here.

blue@blue:~$ counterparty-server kickstart
Running v10.0.0-beta.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 7 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 220, in main
    server.kickstart(
  File "/home/blue/.local/lib/python3.11/site-packages/counterpartylib/server.py", line 555, in kickstart
    kickstarter.run(
  File "/home/blue/.local/lib/python3.11/site-packages/counterpartylib/lib/kickstart/__init__.py", line 344, 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 176, 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

No

if your bitcoin blocks are not stored in the default location you have to pass --bitcoind-dir I think.

please give that a try and lmk if that solves the issue.

Blocks were processing with start

I understand but kickstart reads directly from the block files

rather than using the rpc interface

Same. But blocks are elsewhere. Is there a —blocks-db-dir option?

Or in a conf file for continuity later?

sorry not sure I follow, are you asking if there's a config file for counterparty where you can set the bitcoind-dir?

Bitcoind and blocks are on different mount points

if you pass the path to blocks directory to --bitcoind-dir does kickstart still fail?

/home/blue/.bitcoin for butcoind

/mnt/sda/blocks for chain data

oh sure /home/blue/.bitcoin is just your bitcoin.conf right

please try: counterparty-server kickstart --bitcoind-dir=/mnt/sda/blocks

No go. Different errors.

(I just restarted kickstart and parsed 4000 blocks in 1min30secs

It seems like something is expecting a standard install. Looking for blocks and chainstate in same dir

Treating bitcoind-dir the same as blocks-dir or something like that

will get back to you asap. i haven't tried a setup like yours before

/Chainstate stays in .bitcoin. /Blocks are stored on a different hdd for future proofing and making life difficult.

yeah okay this is a setup that may not be supported atm. good find!

blue@blue:~$ counterparty-server kickstart --bitcoind-dir=/mnt/sda/blocks
Running v10.0.0-beta.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...
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 220, in main
    server.kickstart(
  File "/home/blue/.local/lib/python3.11/site-packages/counterpartylib/server.py", line 555, in kickstart
    kickstarter.run(
  File "/home/blue/.local/lib/python3.11/site-packages/counterpartylib/lib/kickstart/__init__.py", line 328, in run
    last_known_hash = get_last_known_block_hash(bitcoind_dir)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/blue/.local/lib/python3.11/site-packages/counterpartylib/lib/kickstart/__init__.py", line 146, in get_last_known_block_hash
    chain_parser = ChainstateParser(os.path.join(bitcoind_dir, 'chainstate'))
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/blue/.local/lib/python3.11/site-packages/counterpartylib/lib/kickstart/blocks_parser.py", line 334, in init
    self.ldb = open_leveldb(leveldb_dir)
               ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/blue/.local/lib/python3.11/site-packages/counterpartylib/lib/kickstart/blocks_parser.py", line 31, in open_leveldb
    return plyvel.DB(db_dir, create_if_missing=False, compression=None)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "plyvel/_plyvel.pyx", line 247, in plyvel._plyvel.DB.__init__
  File "plyvel/_plyvel.pyx", line 94, in plyvel._plyvel.raise_for_status
plyvel._plyvel.Error: b'Invalid argument: /mnt/sda/blocks/chainstate: does not exist (create_if_missing is false)'

yeah counterparty assumes chainstate and blocks dirs are in the same directory

Look above at error on line 146

yeah i understand

Trying to traverse to /chainstate but using the wrong dir as root

your blocks and chainstate dirs have different parent directories. counterparty-server doesn't support that

you found a documentation bug

well done 🙂

Thats why I’m doing it the hard way.

can you move them to the same dir?

Not today

Well

(fyi just passed block 300k in 10 mins. kickstart is a lot faster!)

I can but that wouldn’t fix the problem. I can only move it one way and that wouldn’t work.

okay well in any case you will not be able to run kickstart in your current setup. when you get a chance if you could make it so that blocks and chainstate are in the same dir and try again that'd be super helpful

I think it is also that counterparty is assuming everything is in the .bitcoin dir.

ah also run develop — the non-determinism I mentioned should be fixed

it does, unless you pass bitcoind-dir, but then it assumes _all_ your bitcoin data is there

I’m on alpha

Can counterparty be made aware of bitcoin.conf? That holds the blocksdir setting.

ah yeah idk

i mean i think for now the best thing is just to document what we don't support and maybe file issues for this for a later release

We can make kickstart be the default for initial non-bootstrap sync… which I assume is the plan?

so @teysol can explain in more detail but it's challenging to get kickstart to work with simplenode and since kickstart will be obviated with v11 it would not be a huge payoff.

Going through kickstart init.py, chainstate is assumed to be subdir of bitcoind_dir. I hard coded it for chain_parser but there are other references I dont have the attention span to dig into rn.

it's challenging because docker is designed for running stateless services, and kickstart requires interaction

It's solvable, but only inelegantly

and we're likely gonna to delete all of the relevant code Soon(TM)

Thats my style. Tell me more

there's nothing to tell. come up with a hack if you want to! IMO we have higher priorities

I only have gitlab for work, I will make a github for personal use another day, could you please summarize and post your thoughts about this issue?

Here is my error after hard coding the path to chainstate…

blue@blue:~/.local/bin$ counterparty-server kickstart --bitcoind-dir=/mnt/sda/blocks
Running v10.0.0-beta.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 7 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 220, in main
    server.kickstart(
  File "/home/blue/.local/lib/python3.11/site-packages/counterpartylib/server.py", line 555, in kickstart
    kickstarter.run(
  File "/home/blue/.local/lib/python3.11/site-packages/counterpartylib/lib/kickstart/__init__.py", line 344, 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 176, 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

Also, I installed manually if you were not reading along.

this is a bug! please file an issue! 🙏

Another day. My other life is calling me.

Is it ok that I also hard coded a check for the newest version of addrindex? I think it was 0.4.4 and I changed the check to expect 0.4.6.

Nope. No compatibility between unsupported versions is guaranteed.

Well, I somehow installed addrindexrs 0.4.6.

0.4.6 is the newest version. Released two days ago, credits to you.

The check for which addrindexrs version needs to be changed *somewhere* I lost where

it's fixed on develop

there are tagged versions of addrindexrs so that you can install the one appropriate for the version of counterparty-core you're running

but again we're killing addrindexrs asap

(btw for those keeping track I've now parsed 100k blocks in 1hr17mins 😁)

each version of counterparty-core requires a specific version of addrindexrs https://github.com/CounterpartyXCP/counterparty-core/blob/6f5e4e417bda336e6630b65d214dcf89710b5e6e/counterparty-lib/counterpartylib/lib/config.py#L18

if you do not run that version, things will obviously break

I’ve waited over two years, I’ll wait longer.

If you want me to try again, let me known how you want me to delete addrindexrs and reinstall 0.4.4

Otherwise I’ll wait for a new version of counterparty sans addrindexrs or a version of counterparty that uses 0.4.6 to continue.

if you run develop on counterpart-core you should have no issues with addrindexrs. alternatively you can downgrade addrindexrs to match the version required by your version of counterparty-core

in either case when the v10 is officially cut it'll require a specific version of addrindexrs. the volatility of the dependencies is part of the release process (and the fact that addrindexrs exists obv)

Sure. I’m not as experienced with the revisioning via git as some but I grasp the concepts and understand what you’re saying. Is the alpha the same as the develop in this git world? Counterparty start works, kickstart doesn’t; with a manual override of the addr version check.

alpha is not develop, it's a version tag; it doesn't change. develop is the branch PRs are merged into; it's changing constantly and is the "bleeding edge".

afaik the alpha works with addrindexrs 4.4 so you can downgrade addrindexrs from 4.6 to 4.4

Show-params says I’m on 10.0.0-beta.1

I followed the develop readme as best as I could to end up here.

What is the correct git clone command to get the develop branch?

in general it's best to wait for the actual release. that's the only time there's a guarantee of stability (not that it'll be perfect)

I’m not worried about stable right now. I’m here to beta test if you want.

I appreciate that, but the only value in beta testing is finding issues to file on GitHub. informal testing with mismatched versions and no bug reports is, unfortunately, not helpful

https://t.me/xcpdev/10302

fyi with kickstart i hit block 500k in 4hr30mins

i get this error... on testnet

i solved just changing a codelina

addrindexrs:
image: counterparty/addrindexrs:v0.4.4

Yeah the difference is too much. I’ll switch to direct after the docs get updated

the correct soln to the failed version check is not to change the code but to update the dependency. older versions of AddrIndexRs have known bugs and incompatibilities

what docs need to be updated?

So my node is fully synchronized now

congrats!

so 6 days?

i think that's the first sync on v10 with start...

What's your latest message_index?

I am finishing my kickstart sync right now. why do you ask?

I have something quite different than before, my message index is only 5m something

5138587|836802|insert|dispensers|{"tx_index": 2719506, "tx_hash": "eae0de62bf14169cadd7e51457a58df9ba08b872f3747fa959aaa9b2af2c3a1e", "block_index": 836802, "source": "1Hb5UDeRECUxPwf9Z9t9n3guAzTF9nkDGA", "asset": "WUPEPE", "give_quantity": 1, "escrow_quantity": 300, "satoshirate": 100000, "status": 11, "give_remaining": 296, "oracle_address": null, "last_status_tx_hash": "f89ba074bf17550b92165cf0459042ba3ba467027715990f828cf2bd06b49de0", "origin": "1Hb5UDeRECUxPwf9Z9t9n3guAzTF9nkDGA", "dispense_count": 4}|1711721058

that's the latest

So I've never worked with the messages table before but it's not consensus critical and I am guessing the change has something to do with removing UPDATEs?

as part of v10 checkpoints were added from the last checkpoints (in 2016) up to ~the current block height. so if there were a consensus break it'd be caught.

Oh, that's why

I will need to rework my parser

I was wondering if I missed some data

now that we have updated checkpoints your node will crash if you do :)

The previous message index was like 2x the current. Which makes sense without the UPDATE