- 01 April 2024 (11 messages)
-
Someone? Anyone? I'd like to send messages.
-
how do i fix it?
-
-
i am a telegram admin apparently but i do not know how to do anything. if you tell me how to allow you to chat I will make it happen
-
-
-
I'll see if I can fix this...
I've sent you a new invite link -
While we’re on the topic, please unban me from Official Counterparty chat. It shows as private group for me. Thanks to any admins of that group who can help.
-
Why were you banned?
-
No idea
-
Haven’t had access for quite some time
- 02 April 2024 (22 messages)
-
You were banned by the bitchslapperbot. I added you back.
-
I'm too
-
Can you add me in the Official Counterparty chat
-
*Extremely few* bugs have been reported for any of the pre-release versions of v10.0.0... and we're planning on making the release soon. If you are running infrastructure and haven't fully tested everything yet (at least on a beta), please do so *ASAP*. Otherwise expect things to break horribly. There is nowhere near suffucient test coverage of the codebase yet to have any guarantees that there won't be accidental regressions.
Don't wait to catch up using start. Use kickstart (just published these instructions for doing kickstart with Docker https://docs.counterparty.io/docs/advanced/how-to/docker-kickstart/) or bootstrap (to test the API).
You can test it out at api0.counterparty.io. -
None
-
adam are you running api.counterparty.io?
-
-
what port is api0 on?
-
-
-
Lol how does this bot determine bans?
-
“Bans known links and keywords”. Not sure what those links and keywords are though. Just happy to be back.
-
Ah ok so same api server it’s been on
-
-
-
I think I was the only one using xcp-proxy lol
-
No worries tho, not a big deal
-
Some sort of websockets support would be awesome, xcp-proxy was very buggy and needed to be restarted often
-
-
The Rise of Alternative Virtual Machines (AltVMs)
There are numerous attempts underway to develop an alternative virtual machine to our familiar EVM. Let's dive in.
-
-
- 03 April 2024 (8 messages)
-
The replacement for api.counterparty.io is up at api0.counterparty.io. _Please test it out!_
Expected changes
* Running Counterparty Core v10.0.0-rc1
* No xcp-proxy, Counteblock or AddrIndexRs
* SSL only
See https://api0.counterparty.io -
Deserializando una transaccion de counterparty - BLOCKLACK.com
Como decodificar una transaccion de counterparty en el protocolo de metascript de OP CODES de Bitcoin.
-
just a tutorial in Spanish on how to deserialize a CP transaction
-
Will test this weekend
-
rpc:rpc or public/open?
-
Info is in the link
-
I was confused too when we were talking about api0 the other day and I did an rpc call from postman and it returned the html lol, then I realized I just needed to click on it
-
I’m a da. Thanks
- 09 April 2024 (1 messages)
-
🎉 Counterparty Core v10.0.0 Released! 🎉
Official Release Notes: https://github.com/CounterpartyXCP/counterparty-core/releases/tag/v10.0.0
This is a *huge* milestone for the project, providing a strong foundation for future releases and major improvements to the Counterparty platform. Thanks to everyone in the community that contributed to the release and testing. 🙏 - 10 April 2024 (78 messages)
-
What is the purpose of not being able to open a dispenser on another address unless it has no balance history?
-
Users are required to either move their assets to a reuseable wallet and open up the dispenser there, or generate one time use wallets for each asset sale.
It seems unnecessarily restrictive -
**Show-stopping bug was just triggered on mainnet.** It's affecting both v10.0.0 and v9.61.1:
https://github.com/CounterpartyXCP/counterparty-core/issues/1619counterpartylib.lib.exceptions.ParseTransactionError: index out of range · Issue #1619 · CounterpartyXCP/counterparty-core10|counterparty | ------------------------------ start ------------------------------ 10|counterparty | [2024-04-10 02:48:04][INFO] Connecting to address indexer. 10|counterparty | [2024-04-10 02:4...
-
sorry. Tried to open a dispenser with the api… bad derp
-
Lol
-
-
You should get a special asset..
-
-
Joined.
-
Joined.
-
-
-
-
Derped it! :)
-
-
-
-
I can't update in the [fednode update counterparty counterparty-testnet] Is there another way
-
hey, can i still use federated node or should i move to counterparty-core?
-
-
-
from what I remember there was a time a user could open a dispenser on an address not controlled by them (like a public exchange address) and create 'false liquidity' on assets by a dispenser being triggered by those pre-planned tx's on that specific address
-
Yea, dispensers were set up on exchange hot wallets. Triggered thousands (if not 10s or 100s of thousands) of "fake" dispenses.
This happened around a year ago, resulting in several anti-spam rules added to dispensers. The no btc history restriction was one of them. -
(I'm not a fan of calling stuff "spam". Someone discovered a creative way to distribute their token. The problem was a disproportionately low fee. With one btc tx fee, they distributed the token to thousands of addresses)
-
Joined.
-
-
-
no worries
-
right click on the web page, choose "inspect element", and open the console tab on the popup
-
and share a screenshot of that page.
-
Joined.
-
if only there were a way of tying the cost of a transaction to its complexity... 🤔
-
-
no worries! happy to help
-
-
-
what's the URL of that page?
-
-
-
-
ah hm okay this is an xchain thing at first blush.
-
@teysol anything we can do here?
-
-
sorry, what are you uninstalling and reinstalling? Freewallet?
-
Any issues with api.counterparty.io? Seems to be down right now
getting "no healthy upstream"
Note: using HTTPS / port 4000 -
appreciate that @ChiefSamyaza !
-
Thank you thank you thank you for explaining and thank you again Periwig for the help
-
I’m reading I just go in and change right?
-
-
-
-
-
okay yup, another bug. restarting the servers fixes it. currently investigating
-
-
-
-
This worked
-
-
-
great to hear 🙂
-
-
-
-
-
-
Yes there is.
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
-
The revision version bump is included also. It works, is what was done in the xcp.dev node which is up and running fine now
-
Commits · CNTRPRTY/counterparty-lib
Counterparty Protocol Reference Implementation - Core Version - Don't trust, verify - Commits · CNTRPRTY/counterparty-lib
-
-
I missed some steps in the release procedure in the rush last night. See https://github.com/CounterpartyXCP/counterparty-core/issues/1626Correctly Bump Versions for v9.61.3 and v10.0.1 · Issue #1626 · CounterpartyXCP/counterparty-core
I botched the release a bit by not following the procedure (was in a rush). Update VERSION_ variables in lib/config.py Update protocol_changes.json (as necessary) Update Counterparty package versio...
-
-
Joined.
-
how do i get the wallet working now?
-
it seems like alot of manual work is there a video with steps up?
-
Hi everyone
Just finished at work and wanna let you know it’s all working
Thanks for the help again -
what is the process?
-
Maybe a video can update everyone follow the steps
-
Assuming you’re using FreeWallet: In your FreeWallet server settings, make sure that CP SSL is set to Yes. That’s it!
- 11 April 2024 (20 messages)
-
ok i got too many server options
-
which one did you guys use?
-
i thought api0 or api1 would word but nope
-
Joined.
-
hey, im trying to run new counterparty-core using "Getting Started" and by this:
git clone git@github.com:CounterpartyXCP/counterparty-core.git
cd counterparty-core
mkdir ~/.local/share/counterparty-docker-data
docker-compose up -d
After running docker-compose up -d i get:
WARN[0000] /home/cpd/counterparty-core/docker-compose.yml: version is obsolete
[+] Running 0/1
⠼ Container counterparty-core-bitcoind-1 Starting 0.4s
Error response from daemon: error while mounting volume '/var/lib/docker/volumes/counterparty-core_data/_data': failed to mount local volume: mount /home/cpd/counterparty-core/${XDG_DATA_HOME:-~/.local/share}/counterparty-docker-data:/var/lib/docker/volumes/counterparty-core_data/_data, flags: 0x1000: no such file or directory -
Is there anyone else who was able to get wallet functioning back to normal?
-
I need to get my wallets back working are you willing to show me how to manually fix mine?
-
Freewallet?
https://twitter.com/FreeWallet/status/1778229788605620371FreeWallet (@FreeWallet) on XAny FreeWallet users who are experiencing "API Communication" issues, it is because https://t.co/JHJCSiNahS no longer supports HTTP requests. If your getting the error, make sure your "Server Settings" match the screenshot below TLDR... Set "CP SSL" to "Yes
-
-
None
-
-
-
it says Error while trying to sign send trasaction
-
😒
-
feel free to continue discussion about it in the FW chat below
there is a user manual pinned in that chat that has a couple solutions for that error
https://t.me/freewallet_ioFreewallet.io ChatThis is a channel to discuss FreeWallet and ask questions and let the community answer
-
is this where everyone is talking about it?
-
that is where we publicly discuss all things freewallet and that error you are getting is very common but has a few steps to try if its happening - just dont wanna clog up XCP dev chat with FW stuff
-
I wrote this gist up below a while back for 0.9.23
but steps usually goes like this;
1. check what version you are using (should use latest 0.9.29)
2. check your SSL settings are correct as above
3. try enabling or disabling any VPN you are using
4. restart freewallet
5. restart your computer
6. if it has to do with your BTC balance or UTXO's then you have to consolidate your UTXO's on the address (most users use the Electrum wallet to do so)
https://gist.github.com/davestaxcp/1e2cc086a13c9a2d045876852b57e5be#error-while-trying-to-broadcast-transactionFreewallet FAQ 2023 v0.9.23 - Write Up - Draft #5Freewallet FAQ 2023 v0.9.23 - Write Up - Draft #5. GitHub Gist: instantly share code, notes, and snippets.
-
ok nice steps but still getting a bunch of errors
-
seems like some wires are patch wrong somewhere
- 12 April 2024 (33 messages)
-
So you want to add insult to injuries is that it?
-
Jeremy has been nothing but cordial AFAICT. You on the other hand threatened him with spurious legal action.
-
Lmfao
-
-
Being a maintainer of an open-source project is generally understood to be unpleasant and thankless. I don't understand why people abuse those who are volunteering their time.
-
@AryanJab you still need tBTC?
-
I'll take some, sure. But Joe hooked it up. I always need some though. Too poor to test on mainnet like some of you ballers.
-
lol, testing on mainnet is a weird status flex in any case. Syncing my node, please post an address and I'll send some over.
-
tb1q75dtzykyxwe80rn3mnv2hpxtl4zawuncyhk8t2
-
-
i found some in a 9yo testnet counterwallet
-
-
-
-
Is this the Phoenix J-Dog account? Rising up from the ashes and shit?
-
-
Joined.
-
@herpenstein would you try http://api1.counterparty.io:4000?
> http POST http://rpc:rpc@api1.counterparty.io:4000/api/ jsonrpc="2.0" id=1 method="get_running_info"
HTTP/1.0 200 OK
Access-Control-Allow-Headers: DNT,X-Mx-ReqToken,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Authorization
Access-Control-Allow-Methods: GET, POST, OPTIONS
Access-Control-Allow-Origin: *
Content-Length: 890
Content-Type: application/json
Date: Fri, 12 Apr 2024 21:02:02 GMT
Server: Werkzeug/2.0.3 Python/3.6.9
{
"id": "1",
"jsonrpc": "2.0",
"result": {
"api_limit_rows": 1000,
"bitcoin_block_count": 838917,
"db_caught_up": true,
"indexd_blocks_behind": 0,
"indexd_caught_up": true,
"last_block": {
"block_hash": "000000000000000000015f1d89e6f281a6812a4b14774aaf2db5e08b0e17fe76",
"block_index": 838917,
"block_time": 1712954885,
"difficulty": 86388558925171.02,
"ledger_hash": "13c008a33d762ec45d33a4959b30e4252b172b49e72eae62888020d81836cd4d",
"messages_hash": "6e8f4efaf9dbba05cae9ea015b55f1e2eb6409f45786fb8b93ffda0501995137",
"previous_block_hash": "000000000000000000020ecbec95045babd12d1f1799e08df01a8401773f3916",
"txlist_hash": "9ea72d4ca3deef53eb8aabeeff0f17eee95ae3221bb222b980ae3c335c8b2746"
},
"last_message_index": 10653997,
"running_regtest": false,
"running_testcoin": false,
"running_testnet": false,
"server_ready": true,
"version_major": 9,
"version_minor": 61,
"version_revision": 1
}
} -
Générâtes fine
-
-
Transaction.py line 833 sets desired to b”” when there is no cp data (create_send with asset btc), but the returned data is b”\r\\x00”
-
So i think that is part of the problem.
-
-
Another bizarre behavior is the parsed source sometimes returns the incorrect address
-
Line 871
-
Unfortunately I’m out of time for the evening
-
okay. if you find anything else, just include it in the issue https://github.com/CounterpartyXCP/counterparty-core/issues/1648
-
-
Kk I’ll add these notes right now
-
Ser if you don't spend your fridays hunting for bugs in blockchains then what are you even doing with your life 🙄
-
Kk threw some notes up. I think there’s two problems, one easy to fix and one a little more difficult, but I’m wrong a lot :-p
-
-
Joined.
- 13 April 2024 (41 messages)
-
Should this endpoint be presented as a temporary work around to the community?
-
Joined.
-
2Mz2v54yrfR276y16yEsh81Uu8A1BHuDBgE
does anyone have tbtc and xcp from testnet to give to me? -
Pepeople, meme collectors, gangsters , hedge funds, trumpetors, stampardos, OGs, shitcoiners and any kind of frogs. in May we will have an event in Barcelona to talk about Counterparty, and historical NFTs and some OGs will talk about their crypto experience in the early days.... If any of you are in a Coounterparty project, or you know Bitcoin since early years and you have been participating in projects and you can prove it. Dm me.. I would like you to be able to attend.
-
Can you send me too... ?
-
Oh thanks mate sorry sorry
-
hey, i have a question about manual installation of counterparty-core. In instructions there is a step:
Install the counterparty-cli library:
cd counterparty-core/counterparty-cli
pip3 install .
but in git repo, there is no counterparty-cli folder/directory -
good catch, readme needs to be updated
-
-
so what should i do now? :D i cant finish installation
-
-
ah okay
-
yes, sorry. using the readme for installation instructions is so last week.
-
ok, now another question. How do i start counterparty, if i did manual installation?
counterparty-server start/kickstart/bootstrap does nothing "command not found" -
and another typo on website in docs:
-
-
-
docs don't say to do that tbf
-
-
-
they're out of sync with master actually
-
well ofcourse not, was following instructions :D thanks for that
-
-
so last step after installing rs, lib, wallet, should be core?
-
-
-
so website need one more update
-
yeah, after installing everything (rs, lib, wallet, core) cant run via "counterparty-server start" get "counterparty-server: command not found"
-
i guess first i need to create it as a service, to point somewhere?
-
you're on master?
-
yes
-
If you follow the installation instructions and get this error then there's a bug (even if it's just in the docs). Please file an issue providing steps to reproduce.
-
-
so if doing manual installation, it should create a service called "counterparty-server" after installing counterparty-core?
-
ok, nevermind, i fixed it
-
what was the issue?
-
problem was, that it wasnt added to path correctly.
I runned:
find ~/ -type f -name counterparty-server
It found as:
/home/cpd/.local/bin/counterparty-server
So i added it permanently to my path:
echo 'export PATH=$PATH:/home/cpd/.local/bin' >> ~/.bashrc
Then reloaded to apply changes:
source ~/.bashrc
Now server up and running :) -
great yeah! was thinking/hoping it was just a path issue :)
-
and i see that counterparty-server is not a service so you have to keep ssh shell open or detach from it. I can paste in here small instructions on how quickly make it on ubuntu as a background service :)
-
Create a file in systemd for counterparty-server service:
sudo nano /etc/systemd/system/counterparty-server.service
Info for the file:
[Unit]
Description=Counterparty Server
After=network.target
[Service]
User=cpd
Type=simple
ExecStart=/home/cpd/.local/bin/counterparty-server start
Restart=always
RestartSec=10
[Install]
WantedBy=multi-user.target
save it;
Reload it:
sudo systemctl daemon-reload
Enable service:
sudo systemctl enable counterparty-server.service
Start service:
sudo systemctl start counterparty-server.service
Check status of the service:
sudo systemctl status counterparty-server.service
Check the log of service:
sudo journalctl -u counterparty-server.service -f -
what address type is the parsed_source where you get this error? or does it not matter?
- 14 April 2024 (2 messages)
-
I made a gh issue about this last week.
-
Can’t check atm, but I definitely tried native segwit to native segwit and had the error.
- 15 April 2024 (4 messages)
-
Just NB there are two issues outstanding that may affect stability:
- Intermittent broadcasting issues: https://github.com/CounterpartyXCP/counterparty-core/issues/1656
- AddrIndexRs nonsense: https://github.com/CounterpartyXCP/counterparty-core/issues/1663Issue Broadcasting Transactions?? · Issue #1656 · CounterpartyXCP/counterparty-coreI have no idea what this is.
-
Not sure whether there's total overlap b/t this channel and the general chat, so cross-posting known issues with v10. haven't gotten any new bug reports in the last 12ish hours but if you come across problems *please file issues* and provides steps to reproduce, screenshots, logs, etc. here: https://github.com/CounterpartyXCP/counterparty-core/issuesIssues · CounterpartyXCP/counterparty-core
Counterparty Protocol Reference Implementation. Contribute to CounterpartyXCP/counterparty-core development by creating an account on GitHub.
-
Is the btc blockchain reorganizing itself?
-
Or is it just freewallet?
- 16 April 2024 (14 messages)
-
The public API servers at api.counterparty.io look to be very stable now, with all known regressions fixed. Now preparing a new release with those patches (and more) included.
-
-
-
-
Joined.
-
New Release of Counterparty Core: v10.1.0.
This release fixes a number of long-standing bugs, in addition to some regressions in v10.0.x. It has already been running on api.counterparty.io for the past 24 hours and been shown to be stable. The full release notes are available on https://github.com/CounterpartyXCP/counterparty-core/releases/tag/v10.1.0Release v10.1.0 · CounterpartyXCP/counterparty-coreRelease Notes - Counterparty Core v10.1.0 (2024-04-16) This release includes fixes for a number of bugs as well as a few regressions in v10.0.x. Upgrade Procedure This upgrade is optional but highl...
-
Love you, dude. Thank you.
-
Joined.
-
Hi, all. Below is an important message about the upcoming API redesign. TLDR: with v10.1.2, APIv2 will be released and APIv1 will be officially deprecated. It will still be supported for some period of time, but its use will be discouraged and it will be removed eventually. We've got some number of weeks yet till v10.1.2 is released, but want to give folks (especially infrastructure providers) as much notice as possible so that they have enough time to migrate over to the new API.
--
In early January, 2024 discussions about improving Counterparty Core's API began on Telegram. Users' primary complaints were that calls were "too slow" and lacking in critical features. Three GitHub issues were created to identify problems with the current API: one for users to request specific additional API calls (https://github.com/CounterpartyXCP/counterparty-core/issues/1299); one to document slow API calls (https://github.com/CounterpartyXCP/counterparty-core/issues/1359), and one to discuss the design of the new API (https://github.com/CounterpartyXCP/counterparty-core/issues/1327). Users were encouraged to comment on all of these issues over the following weeks.
As requests for specific improvements to the API were not forthcoming, issue #1299 was closed on January 29. Adam and Ouziel determined from their own testing that the apparent slowness of the API was actually the result of the necessary client-side filtering users had to do because the API wasn't sufficiently powerful, and so issue #1359 was closed on March 11. The issue for the API redesign (#1327) has been open since January 15, and has received no comments except one on January 16.
Two weeks ago, Ouziel began work on the new API and published the first pull request for a new API ('APIv2'), which includes the specification for APIv2: https://github.com/CounterpartyXCP/counterparty-core/pull/1607. Following the design specified in (#1327), that PR states, when APIv2 is released, the current API ('APIv1') will be deprecated; it will be disabled by default and put behind the route /old/api.
APIv2 is set to be released as part of v10.1.2. While v10.1.2 will not be a mandatory upgrade, api.counterparty.io servers will be running v10.1.2 as soon as it's released, and therefore services which use api.counterparty.io must update their calls to the latter with APIv2's routes. Furthermore, with the release of v10.1.2, APIv1 will be officially deprecated and supported only for a fixed period of time during which users must migrate to the new version. It will eventually be removed. APIv2 will be significantly faster, better-tested, and more user-friendly than v1. On the other hand, it will abstract away a number of implementation details of the current codebase that some developers may depend on today. Of course, if a user or downstream developer wishes to bypass the API and access the Counterparty DB directly, they are welcome to—however, it will be the responsibility of that developer to maintain their own software as the implementation changes. There will continue to exist an endpoint for fetching from the messages table, which may be used for similar purposes and which will be officially supported.Expand API to Support Block Explorers · Issue #1299 · CounterpartyXCP/counterparty-coreIt seems that right now, if you want to create even a simple Counterparty block explorer, you first have to implement a lot of extra functionality in the backend. xchain.io has done this (closed-so...
-
hey all, I need some testnet btc and xcp. anyone able to send either or both? tb1qh0asuzmwye877da2ma45706uplve0mvktxflhf
-
None
-
Hi all! Here is an update detailing recent development work and providing a retrospective on the instability after v10's release: https://www.counterparty.io/post/counterparty-development-update-april-16-2024Counterparty Development Update — April 16, 2024
v10.0.0 ReleaseOn April 9th, Counterparty v10.0.0 was finally released, which represented a huge effort over the past months to begin resolving long-standing issues with the stability, correctness and performance of the Counterparty reference implementation, and to prepare for future feature development. The massive changelog is available on GitHub, marking the first major milestone after a huge acceleration in the pace of development of Counterparty. Nevertheless, v10.0.0 was a conservative rel
-
Where should we leave comments on API changes?
-
I think either the open issue or the pr is fine?
- 17 April 2024 (24 messages)
-
(pls don't get mad at me if @teysol unceremoniously moves the discussion to some different place lol)
-
yeah this is the issue: https://github.com/CounterpartyXCP/counterparty-core/issues/1327API Redesign · Issue #1327 · CounterpartyXCP/counterparty-core
So it turns out that I designed the API very badly 10 years ago. It's insanely leaky and is missing critical functionality. Ideas: Deprecate everything that exposes the DB schema. Use X-API-War...
-
- 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. -
-
thanks @XJA77 ! Any reason you didn't want to use the Docker Compose script in the repo?
-
Is there testnet xcp? Is there a faucet? I can’t find it on testnet xchain
-
Burn testnet BTC.
-
Ah ok 👍
-
Where do i burn it to? Or destroy?
-
does freewallet allow you to burn?
-
-
-
If it’s just to send to a burn address yes. And also destroy
-
-
-
-
-
-
Ah right. Ok boss 🙏♥️
-
-
I promise not to fuk it up
-
-
-
👍
- 18 April 2024 (3 messages)
-
1. Kickstart doesn't work with docker
2. I like this way as I can run diferent versions of counterparty easily
3. Works better for me having it like this to run the stamps indexer easier too -
Kickstart does work with Docker now (https://docs.counterparty.io/docs/advanced/how-to/docker-kickstart/)Docker Kickstart | Counterparty
1) Create a persistent volume
-
- 19 April 2024 (3 messages)
-
I'm experiencing a strange performance issue for this API call, which I often use to look at DEX listings (just let me know if I should create a github issue for it)
v9.61: duration: <1s
curl -X POST http://api1.counterparty.io:4000/api/ --user rpc:rpc --data-binary "{ \"method\": \"g
et_orders\", \"params\": { \"filters\": [{\"field\": \"status\", \"op\": \"=\", \"value\": \"open\" } , {\"field\": \"g
et_asset\", \"op\": \"=\", \"value\": \"XCP\" } , {\"field\": \"get_quantity\", \"op\": \"^>=\", \"value\": \"3800000000
\"} ] , \"filterop\": \"AND\" , \"start_block\": 799000 }, \"jsonrpc\": \"2.0\", \"id\": 0 }"
v10.1.0: duration: 7s+ (often times out at 30s)
curl -X POST https://api.counterparty.io:4000/api/ --user rpc:rpc --data-binary "{ \"method\": \"g
et_orders\", \"params\": { \"filters\": [{\"field\": \"status\", \"op\": \"=\", \"value\": \"open\" } , {\"field\": \"g
et_asset\", \"op\": \"=\", \"value\": \"XCP\" } , {\"field\": \"get_quantity\", \"op\": \"^>=\", \"value\": \"3800000000
\"} ] , \"filterop\": \"AND\" , \"start_block\": 799000 }, \"jsonrpc\": \"2.0\", \"id\": 0 }" -
-
Slow performance on get_orders · Issue #1709 · CounterpartyXCP/counterparty-core
I'm experiencing a strange performance issue for this API call in v10.1.0: v9.61: duration: <1s curl -X POST http://api1.counterparty.io:4000/api/ --user rpc:rpc --data-binary "{ "...
- 20 April 2024 (9 messages)
-
https://testnet.xchain.io/tx/c97954c604bba30c2c79417705cb20150ed55f27b331cd60866d257aa86a5430
look this dispensers remaining 604 but in scrow 5 -
A underflow bug?
-
Nope
-
Dispenser refill:
-
-
Agree it does look confusing but it’s just a display issue
-
Why do I get negative give_ remainings in some dispensers?
-
Which ones?
-
now I'm resyncing the node again
- 21 April 2024 (22 messages)
-
Does anyone know where the bitcoin directory is on macos if you install bitcoin with homebrew?
-
I had mine in ~/Library/Application Resources
-
-
Ugh of course, how foolish of me to think it was in /Library/Application Support
-
Thanks @AryanJab !
-
-
i got this error...
-
interesting haven't seen that. what version? what's your config? steps to reproduce?
-
last version
-
with bootstrap
-
master branch
-
jus docker compose up :)
-
-
https://github.com/CounterpartyXCP/counterparty-core/issues/1655
i think is related to this issue...Weird SQLite Error on Startup · Issue #1655 · CounterpartyXCP/counterparty-core13|counter | [2024-04-14 08:28:05][INFO] Running v10.1.0-rc.1 of counterparty-lib. 13|counter | [2024-04-14 08:28:05][INFO] Running v10.1.0-rc.1 of counterparty-server. 13|counter | [2024-04-14 08:...
-
got it. would you file a bug report please?
-
I wanted to try deleting the cache and the database and start from 0, now I get another error. :)
-
I will investigate what is going on and I will do it.
-
-
new error
-
ERROR:root:SQLITE_LOG: os_unix.c:44373: (2) open(/data/counterparty/counterparty.db) - No such file or directory (14) SQLITE_CANTOPEN · Issue #1722 · CounterpartyXCP/counterparty-core
I upgraded from version v10 to version v10.11 and got a block indexing error, deleted the database and the counterparty folder, redid docker compose with bootstrap and got this error.
-
can you delete the db and try again?
-
i am less familiar with the docker setup, sorry.
- 22 April 2024 (9 messages)
-
ERROR:root:SQLITE_LOG: os_unix.c:44373: (2) open(/data/counterparty/counterparty.db) - No such file or directory (14) SQLITE_CANTOPEN · Issue #1722 · CounterpartyXCP/counterparty-core
I upgraded from version v10 to version v10.11 and got a block indexing error, deleted the database and the counterparty folder, redid docker compose with bootstrap and got this error.
-
with or without bootstrap it fails, I think the addrsindexrs is not available and that's why the counterparty-core startup fails. I had to manually download the botstrap and unzip it.
-
J Loone Brickens 🧱 (@wasthatawolf) on X
PSBTs facilitate trustless trading of UTXO based assets on Bitcoin (inscriptions, runes, BRC-20). There is clear value in binding assets to outputs. However, there's also value in having an on-chain orderbook to trade assets (rare pepes). Soon, Counterparty will have both...
-
Weeen 2.0 sir?
-
-
I think it's the same problem, and I assume it's a race condition.
-
1. address indexer does not start because the bitcoin node has not synchronized.
2. Counterparty does not start the bootstrap download because address indexer has not connected, and assumes that counterparty.db exists. -
I was able to fix it by manually downloading the bootstrap..
-
- 23 April 2024 (22 messages)
-
Is https://api.counterparty.io correct? Maybe I'm late to a change that happened but I'm getting Error: Failure when receiving data from the peer errors when running queries that once worked.
{
"method": "get_assets",
"params": {
"filters": [
{
"field": "asset_name",
"op": "==",
"value": "FLOCK"
}
],
"order_by": "block_index",
"order_dir": "asc"
},
"jsonrpc": "2.0",
"id": 0
} -
Joined.
-
Could you share some specific examples?
-
Bot.
-
Lol
-
Nope I don’t think so :)
-
excuse me?
-
Really? Such an odd first post.
-
Matt has contributed more to Counterparty Core than almost everyone...
-
-
-
-
-
It’s all good. I appreciate the paranoiac posture.
-
little known fact: most people who are good at building blockchains hate crypto culture and hate telegram even more
-
so they don't post a lot.
-
Yeah, I kind of auto-assume bot especially for new arrivals. Sorry, sorry.
-
welcome here ^^
-
I updated this here with the JSON payload.
Let me know if there's anything else y'all need.
Apologies again for the bot accusations. -
thx @AryanJab. @marceh0le wen paid Telegram group? that's the only way to know you're legit.
-
Another idea is to replace your profile picture with a hot Asian woman. That'll help others know you're 100% legit.
-
Aryan is also a bot so he was hoping to have found a friend
- 24 April 2024 (4 messages)
-
None
-
reposting as last message had the wrong version number. APIv2 will be released as part of v10.1.2. Thanks @uanbtc for catching that!
-
Hi, all. I am very happy to announce that there is a PR for APIv2 specification! https://github.com/CounterpartyXCP/Documentation/pull/184
*This is a draft proposal*. Nothing has been finalized. Having said that, v10.1.2, of which APIv2 will be a part, will be released in weeks, not months, and so I'd encourage anyone who's interested (especially infrastructure providers) to review and comment on the proposal.
This is a huge milestone. Special thanks to Ouziel Slama for his excellent work, and yet another heroic effort.API Blueprint by ouziel-slama · Pull Request #184 · CounterpartyXCP/DocumentationOfficial Documentation of the Counterparty Project - API Blueprint by ouziel-slama · Pull Request #184 · CounterpartyXCP/Documentation
-
None
- 25 April 2024 (15 messages)
-
curl --request POST \
--url http://api.counterparty.io:4000/api/ \
--header 'Authorization: Basic cnBjOnJwYw==' \
--header 'Content-Type: application/json' \
--data '{
"method": "get_assets",
"params": {
"filters": [
{
"field": "asset_name",
"op": "==",
"value": "FLOCK"
}
],
"order_by": "block_index",
"order_dir": "asc"
},
"jsonrpc": "2.0",
"id": 0
}'
I'm still at a loss here with what I'm doing wrong. 🙁 -
Tried /old/api. Also no dice:
curl --request POST \
--url http://api.counterparty.io:4000/old/api/ \
--header 'Authorization: Basic cnBjOnJwYw==' \
--header 'Content-Type: application/json' \
--cookie ROUTEID=.api1 \
--data '{
"method": "get_assets",
"params": {
"filters": [
{
"field": "asset_name",
"op": "==",
"value": "RAREPEPE"
}
],
"order_by": "block_index",
"order_dir": "asc"
},
"jsonrpc": "2.0",
"id": 0
}' -
ser
-
it's not live yet
-
will be live with v10.1.2, which will be released in some number of weeks. RFC period.
-
haven't gotten any complaints about api.counterparty.io requests not working. Will look into it.
-
Need to request https
-
Not http
-
Yessir. This was it.
-
-
There is a database somewhere that has all the counterparty asset images.
How do I get this database? -
-
Lmao
-
For anyone else looking
-
JP J in Official Counterparty Chat
Torrent with Counterparty images from xchain, imgur, easyasset etc. It is important for preserving the "art layer" on top of Counterparty. Please seed the torrent if you have 37 GB to spare: https://jpjanssen.com/counterparty-image-archives/
- 26 April 2024 (12 messages)
-
Anyone getting no healthy upstream when hitting the api?
-
Yes I’m also getting that
-
will look into it.
-
Can one of you share your request pls
-
curl -X POST https://api.counterparty.io:4000/api/ --user rpc:rpc -H "Content-Type: application/json; charset=UTF-8" -H "Accept: application/json, text/javascript" --data-binary "{ \"jsonrpc\": \"2.0\", \"id\": 0, \"method\": \"get_running_info\" }"
(using curl on Windows) -
@Niftyboss1 can you try api3 or api4?
-
api3: hanging / no response
api4:
curl: (7) Failed to connect to api4.counterparty.io port 4000 after 2131 ms: Couldn't connect to server -
😬
-
On it.
-
Great 👍
Note that I will be afk for a few hours, unfortunately -
-
Maybe there is no need? Searching the code for TRANSACTION, BEGIN or COMMIT shows results that don’t seem to be used for this…
- 27 April 2024 (45 messages)
-
-
-
-
Thinking that maybe is not by block because it may over-complicate the logic…
But then what about for some specific *transactions* like ledger credits / debits changes? Good or bad idea?
Just curious about why is not used (other than in tests, based on my search results…) -
-
-
Joined.
-
Having issues with rarepepewallet, getting “Error” when trying to send my xcp and btc. Any help would be greatly appreciated
-
I was having problems getting anything to work this morning. Thought it was me maybe.. sends just not confirming..
-
I’ve tried different browsers, different machines, all same thing
-
Rpw and also free wallet..
-
Stampverse.io w/ unisat Dispenser buys and transfers smooth
-
@Pepe_Legbaaa api.counterparty.io has had sporadic instability the last 24hours or so. Can you please open the console and share any logs when you get the Error notice?
-
we've been working on the servers since Derp and Niftyboss first reported errors yesterday. Two issues have been filed and some quick patches have been put in place, but that still may account for the errors you are seeing.
-
@Nywra_Ekaf if you could do the same would be very helpful!
-
@NorthrnSatosh what servers is stampverse using on the backend?
-
if(xhr.status === 200){ //check if "OK" (200)
console.log(xhr.responseText)
var checksuccess = jQuery.parseJSON(xhr.responseText)
//success - chain.so
//callback(checksuccess.status, checksuccess.data.txid)
//success - xchain
if(!checksuccess.error){
callback("success", checksuccess.tx_hash)
} else {
callback("error", "") //otherwise, some other code was returned -
Sorry, when you get the "Error" in RPW please:
1. right-click on the page
2. select "Inspect Element"
3. select "Console"
4. share the output -
Trying to share, can’t find it. Sorry, haven’t spent much time on this side of the computer
-
no worries!
-
no rush on my end just want to try to help.
-
I really appreciate the help
-
no worries. just made a request to api.counterparty.io and everything looks fine, so I may not be able to help too much. pinging @hodlencoinfield in case he has any insight.
-
testing... v2
getassets.js:40
/php/btcGetUnconfirmed.php?_=1714243819976:1
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
wallet.js:2622 0.00004488
wallet.js:2627 201
wallet.js:2636 123G1oTvfZAVjVfnSppWvpCGBYchuYPkiG
wallet.js:2684 false
wallet.js:1941 0.00004488
wallet.js:1989 Array(1)
wallet.js:1990 35512
transactions.js:174 1
transactions.js:211 XCP
transactions.js:212 from cxsdo: 1
transactions.js:221
transactions.js:222 false
transactions.js:223 false
transactions.js:224 0
transactions.js:240
migration.js:238 Array(1)0: {txid: 'c255b0360fd1fbb2876c4e174fe420fdd613e8cd9634b3d924ff10646c830b3e', address: '123G1oTvfZAVjVfnSppWvpCGBYchuYPkiG', vout: 0, scriptPubKey: '76a9140b657d986552d27cd1c6bddbe66a581aebd99e7288ac', amount: '0.00040000'}length: 1[[Prototype]]: Array(0)
migration.js:242 0
migration.js:249 35512
migration.js:262 01000000013e0b836c6410ff24d9b33496cde813d6fd20e44f174e6c87b2fbd10f36b055c2000000006b483045022100d8ef84d3cec8e76bab83417fe38ddd21885d6e15823f825f4ff64c617662ffe702200ed6b8673fcf3246fc60359bb430036aa6bb47e9924607b125acb2001badb0f901210237e80f5697beb62d8f26ce091c308726255c2a25bb61f035b53c2619a4a6198cffffffff020000000000000000306a2e3929a9f2e3b17c825c1421d42ec4df1fca3c6b6b0c53da2d367883a5fc5db61d28e484ea4a154917287c68215aafb88a0000000000001976a9140b657d986552d27cd1c6bddbe66a581aebd99e7288ac00000000
wallet.js:2159 01000000013e0b836c6410ff24d9b33496cde813d6fd20e44f174e6c87b2fbd10f36b055c2000000006b483045022100d8ef84d3cec8e76bab83417fe38ddd21885d6e15823f825f4ff64c617662ffe702200ed6b8673fcf3246fc60359bb430036aa6bb47e9924607b125acb2001badb0f901210237e80f5697beb62d8f26ce091c308726255c2a25bb61f035b53c2619a4a6198cffffffff020000000000000000306a2e3929a9f2e3b17c825c1421d42ec4df1fca3c6b6b0c53da2d367883a5fc5db61d28e484ea4a154917287c68215aafb88a0000000000001976a9140b657d986552d27cd1c6bddbe66a581aebd99e7288ac00000000
wallet.js:2176 -
ah okay you're getting a 500. This is with RPW?
-
yes
-
okay, I can't decode that hex atm lol, but afaict this isn't a counterparty or counterparty.io server issue. Will try to look into it further but I think that we need Joe to weigh in.
-
ok thank you, much appreciated
-
You're just trying to do a regular send, right?
-
yes
-
@herpenstein
-
You can use bytesdust with okx wallet
-
.
-
api.counterparty.io
-
okay so if stampverse wallet functionality is working well then there's not much I can help out with. Sorry :/
-
No problem, thanks for trying
-
Looks like it was my end but I’ll check when I’m home. 🙏
-
I recommend using rarepepewallet.wtf instead of .com
-
Can’t send my xcp from there
-
This is fucking retarded. No way to find my private key on RPW.com?
-
-
I’m trying import to freewallet. I have not found access to my private keys. Not my 12 word pass phrase, or resetting my wallet. No thanks
-
Joined.
-
Your passphrase is your private key, you can always derive the keys yourself if you want
-
I’m an idiot
- 28 April 2024 (32 messages)
-
Thank you, I feel stupid so I’ll shut up. Still a newb apparently. I better be careful. This just makes me realize how much more there is to Bitcoin that some people won’t be able to work through. This was a learning experience 🤙
-
Do what? How does that work?
-
As long as we have those 12 words, our wallets travel where ever we choose. No matter how clunky a service provider is. 🤯
-
Yes but. How do you get keys from phrase?
-
Most favored. Electrum.
-
Import phrase into Freewallet. Click view address.
-
Freewallet.io desktop wallet has a show private key function.
When you have signed in with your 12 word seed, you can switch addresses and reveal the private key for each address generated from your seed. -
So simple, I over looked it, but doesn’t ignore a flaw in RPW.com right now. Heads up. Maybe it was my address, I don’t know, but Thanks for all the advice.
-
not revealing individual private keys was a design decision
-
For sure, I get that now. But I was frustrated, and not thinking quite right.
-
because sometimes people will import a private key into a different wallet, reset their wallet and wonder why the passphrase doesnt reproduce their address
-
Huh, that’s interesting
-
to avoid that, you only reveal addresses
-
Yeah, so it’s a wallet inside a wallet? Does not compute, situation? Lol
-
for example, in freewallet you can import a private key, so now your wallet becomes passphrase + private key
-
or passphrase + multiple private keys
-
Oh shit, I’m not familiar with that
-
maybe im confusing you
-
Like and additional password to unlock?
-
wallet A with passphrase A produces addresses, you want to import one of those addresses into wallet B with passphrase B
-
so you export the private key for an address in wallet A and import just that key into wallet B
-
so now wallet B is not just passphrase B, its passphrase B + private key from A
-
this can be useful to power users, but confusing to less knowledgable users
-
and can result in losing funds if people think passphrase B is all they need to recover all of wallet B
-
So when you open a dispenser, another address, that has a passphrase to access?
-
Or any other added wallet
-
that depends on the address you open the dispenser on
-
It gives you options for different address types, would that be the depends part?
-
Numbers starting with 1 or b, etc…
-
you can pick any address you want from any wallet you want to be the dispenser address
-
you can even pick an address with no private key at all
-
These issues should be resolved now.
- 29 April 2024 (5 messages)
-
Fuun. To fully sync counterparty core without kickstart, took about 14 days:D
-
yeah, regular start is still totally unoptimized :/ (and the speed is probably highly dependent on machine specs, in particular disk latency)
we're working now on replacing AddrIndexRs with a built-in indexer + block fetcher written in Rust, which should allow a node to catch up at least as fast as one can today with kickstart, but without requiring the user to turn bitcoind off -
Nah, at my situation, disk is nvme gen3, with high IOPS, so thats not the bottleneck. But hey, atleast it finished:D
-
sounds a bit like bridging the past and the future would you say that a fair assessment?
-
interesting! not sure what the bottleneck is then. in any case, it'll be different soon :)