- 11 April 2024 (29 messages)
-
There is no mining. Counterparty is a metaprotocol on top of Bitcoin.
-
If you want to learn more you can read the white paper Counterparty's creator, @teysol recently wrote: https://krellenstein.com/adam/get/counterparty-whitepaper_2024-03-29.pdf
-
-
-
trying to mint and freewallet just stuck on generating. I logged off and on and still same issue. Any ideas?
-
👍
-
Try this: In your FreeWallet server settings, make sure that CP SSL is set to Yes
-
-
None
-
This is a shitty post, freewallet is downloaded, the user needs to update their settings.
-
-
-
-
-
-
-
-
Thanks. We need everyone feedback 🙏
-
Yes you’re right, we used FreeWallet code and tried to improve it.
I just thought at this moment that FreeWallet was still down and give another solution for users.
We’re just an actor who try to improve and give more tools to community -
you guys did find a bug ill give ya that, just a little low to tweet at xcp and fw imo
-
this is why no likes you guys
-
Sorry if you guys felt offended. Didn’t mean it
-
-
-
-
which pair on the dex are you trying to fill an order for? - i havent seen this error before - are you on the XCP/BTC pair? because that would be considered a BTCpay order - many users use Dispensers instead to buy XCP
-
Start by Open sourcing your code
- 12 April 2024 (62 messages)
-
Been getting this one occasionally. Not sure what the root cause is, but a retry often generates a correct tx.
Here’s the issue on GitHub. It was updated earlier today by Adam.
https://github.com/CounterpartyXCP/counterparty-core/issues/1119Constructed transaction does not parse correctly · Issue #1119 · CounterpartyXCP/counterparty-coreIt seems that we have an issue with transferring asset ownership to segwit (bech32) addresses, as the API throws an error indicating that the constructed transaction does not parse properly. API Re...
-
Maybe it’s a language thing lol
-
Peut-être
-
-
-
-
Alpha Collectoors, If anyone is in need of a historical counterparty TEST token hit me up, can match last sale, ono, thanks all
-
-
-
-
-
Is the error something like « Error composing send transaction via API: Constructed transaction does not parse correctly »?
-
-
Yeah this has become a problem for me too. I haven’t been able to buy anything with dispensers in days.
Trying to chase it down, it looks like the api almost always fails to generate a tx with create_send and btc as the asset -
Not sure if this is isolated to the public cp api servers or if this is occurring elsewhere?
-
-
Constructed transaction does not parse correctly · Issue #1119 · CounterpartyXCP/counterparty-core
It seems that we have an issue with transferring asset ownership to segwit (bech32) addresses, as the API throws an error indicating that the constructed transaction does not parse properly. API Re...
-
-
-
-
I manually tried at least 50 test cases with different settings and values. This seems to get it every time:
-
{
method: 'create_send',
params: {
source: 'bc1qy25gwr9vdrvxx0w35wa9vrpc3hc5h6rd0p56f4',
destination: 'bc1q7ra8ec9nmzfw96rnayss83lqzcz78gd0hsp2j0',
asset: 'BTC',
quantity: 69420,
allow_unconfirmed_inputs: true,
extended_tx_info: true,
fee: 41882
},
jsonrpc: '2.0',
id: 0
} -
-
-
-
-
Are you running a node on v9? Does that also throw the error?
-
-
-
-
-
update to most current version of freewallet but getting this communication error
-
Dex trade stopped deposits and withdrawals of XCP for technical reasons it mentions. Would we know the issue?
-
-
Counterparty (@CounterpartyXCP) on X
⭐️Counterparty Core v10.0.0 just released! ⭐️ This is a *huge* milestone for the project with over 700 commits and a hundred issues closed. A big thanks to everyone in the community that contributed to the release and testing. 🙏 Release Notes: https://t.co/9nOSUBihNZ
-
Updated - 6579 XCP available on verified dispensers
https://xchain.io/tx/23bccae79a5c2a58cd1f205ebe099e99c0d0a81f813c7496335ba0ce9eae5174 -- 0.00018000 -- 600 XCP
https://xchain.io/tx/f11d6d4d6e346d7758555bd6c03737a805e233239effdd41e69d91babbb0db4a -- 0.00019500 -- 365 XCP
https://xchain.io/tx/d4ff644f16f54779e25bec6ad80150373e1a26c42ab8709bad100d9272692dd4 -- 0.00020885 -- 1825 XCP
https://xchain.io/tx/22deea485b5a76cc40cc1c0cb1e51f86fbd6ec75053acb532f15773a66f8e2ba -- 0.00021950 -- 300 XCP
https://xchain.io/tx/8341a8a21a30ea3e294dff97ef56849962eec92a3c2b82eb1c89372d78b9c5f4 -- 0.00022000 -- 94 XCP
https://xchain.io/tx/65f367cd9628d4bf9888741c0eb83fb078863029fc6af8178b673f26ded75c85 -- 0.00022800 -- 246 XCP
https://xchain.io/tx/ff299c8face1fe73c34fc3fce39a4d1182b496d53b940ecbdb3612dfa657a267 -- 0.00023000 -- 234 XCP
https://xchain.io/tx/852277eeda9a25194d9c09650193da474eb2600995ee968d8f70e45892b0fdf7 -- 0.00023300 -- 250 XCP
https://xchain.io/tx/5eebfadb25430a7aa6439ded6be53ebf0303b783045e8ca4091b4c246c346b08 -- 0.00024000 -- 874 XCP
https://xchain.io/tx/629f0a2001d763d976316ce4adfbfc8e852096b920cbf0ab778b53618abb3a7a -- 0.00024690 -- 1791 XCP
- As always just DM me if any questions or issues with these dispensers -
Yeah I'm getting this. Also updated freewallet (macOSX) and now its not opening
-
Cp ssl yes
-
Ah yes just seen the tweet about ssl. But now cant open freewallet
-
Do u have to change the use SSL as well on the other net?
-
Yes I removed and reinstalled but still not opening. Are you on mac?
-
BTW is anyone able to make a dispense (from any dispenser at all) today?
It seems there's only been 2 dispenses in the past 24 hours, which is highly unusual -
Derp in Official Counterparty Chat
Yeah this has become a problem for me too. I haven’t been able to buy anything with dispensers in days. Trying to chase it down, it looks like the api almost always fails to generate a tx with create_send and btc as the asset
-
-
Been trying for near 2 days no luck
-
-
Not sure, I can check in about 30 minutes.
-
Do they have any documentation? Or just the splash screen with Loren ipsum
-
-
How did you know they provide a node?
-
because they said so ser
-
this is @Jpcryptos company
-
That node also returns the doesn’t parse correctly error
-
Perhaps something with the actual dispense is causing the issue. That dispenser triggers at 69420 sats and I can do a create_send for 69419
-
And that works fine, but any number triggering the dispense fails with the parse error
-
69420, 70000 etc
-
is the address which is calling the dispenser itself dispensing?
-
No
-
Nothing that fun
-
Just a normal dispense
-
Any word on resolution?
-
- 13 April 2024 (56 messages)
-
👍
-
Justa public node with the last version of Counterpartycore.
-
Just need to make sure this on the real, please confirm for me before I click.
Trying to resolve the issue still -
what are you trying to do
-
-
thats a scam link, it makes no sense in the context of counterparty
-
parsing error makes no sense, to buy from dispenser you just send btc
-
offtopic
anyone with rarepepe discord link?
xcp on discord seems not to be working -
i try sending and it come up parcing error
-
you just need to send bitcoin to the dispenser address, there is no parsing involved
-
thats what i always do, now it not working for while
-
Freewallet.io Chat
This is a channel to discuss FreeWallet and ask questions and let the community answer
-
is that whats going on? is everyone else having same issues?
-
i saw that. do i have to actual install coin daddy or just change the setting?
-
didnt work says counterparty api communication error..
-
The password is different for the coindaddy node, I think it’s 1234 not rpc
-
have to change it on both nets?
-
sorry didnt see bottom of the screenshot.
-
-
no worries at all, you guys are crushing it. thick frog skin here
-
-
-
-
-
-
WHAT???????, I never thought this would happen
-
I don't send any messages to anyone, unless they talk to me first
-
No worries, totally took him for scammer right off.
Least him on for a bit and tried to get him to send me corn🤣🤣 -
What's the difference between win32 and win64? Bout to download freewallet on my pc. Or is there another app to use?
-
It's cpu structure
-
Win64 doesn't work on too old computers
-
wtb xcp in bulk
-
-
-
Join the club😎
-
-
sent dm
-
-
Beware of scammers. Many scammers around these days
-
i have sent you dm bit earlier today, if you can check it Nifty
-
I’m in a (long) meeting right now… Will be sure to check DMs later today!
-
have a good meeting. thank you, no rush on that :)
-
-
-
Doesn’t sound very Stack like
-
-
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.
-
-
Sooooooon
-
Any luck on that yet? 🙏
-
-
It's been 24 hours since the last communication. Debugging is ongoing. Having said that, here's a recap of what's happened as I understand it:
1. The bug that Derp accidentally exploited which took down the network had existed in the wild long before we got re-involved. That it had never been triggered before is dumb luck and is almost certainly on account of the fact that almost no one ever used Counterparty except through Freewallet and RPW.
2. Following (1), Adam discovered the issue and deployed a fix the same night. He had to make a choice to enforcing SSL connections to api.counterparty.io servers, which caused problems with Freewallet. I don't want to speak on Adam's behalf about what went into that decision but this is a standard web practice. In any case this transition was more rushed than it would have been on account of (1).
3. In spite of a month-long release cycle it seems that extremely little manual testing was done by the community. Consequently issues which should have been caught in pre-release versions are being caught now. As I understand it the network is currently being affected by two seemingly related issues: i. constructed transactions do not parse correctly; ii. dispensers have stopped working. (i) has been an outstanding issue for *3 years* (https://github.com/CounterpartyXCP/counterparty-core/issues/1119) but is surfacing much more often with v10; (ii) is currently under investigation.
3.a We will do more automated and manual testing of the API for future releases. HOWEVER: for a community which prides itself on how decentralized it is, it's absolutely unreasonable to expect to offload all responsibility for doing QA onto the maintainers.
4. We are incredibly thankful for all the work Jdog has done for Counterparty over the years, but before making any statements about the state of the software between version 9.61.x and 10 I suggest you take a look at the changelog for version 10 (https://github.com/CounterpartyXCP/counterparty-core/releases/tag/v10.0.0) and the amount of work that was done and the issues that were addressed (https://github.com/CounterpartyXCP/counterparty-core/milestone/12?closed=1).Constructed transaction does not parse correctly · Issue #1119 · CounterpartyXCP/counterparty-coreIt seems that we have an issue with transferring asset ownership to segwit (bech32) addresses, as the API throws an error indicating that the constructed transaction does not parse properly. API Re...
-
Let us know how can we help debug as most of us use freewallet on the daily and can test simple features to make sure the primary wallet runs on the latest updates
-
Appreciate that. IMO we've got to figure out the right way to expose different versions of the software to services that use api.counterparty.io servers on the backend.
-
We've got someone to help with system administration and devops but his availability is intermittent. Hoping to get more consistency in that working relationship. He'll also be helping to bring counterwallet back online.
-
We appreicate more open source wallet options, but the fact remains that freewallet is the choice 99% of us trasnact with daily. Is there a more iron clad way to ensure basic features of free wallet work before implenting changes. I know our groups would be happy to help
- 14 April 2024 (100 messages)
-
“If things are not failing, you are not innovating enough.” Elon
-
Indeed still very bullish but hopefully we cannot break everything in the process. Gotta keep the sats flowing
-
-
Super bullish! Keep breaking stuff.
-
Is there a working wallet to set up dispensers?
-
Yeah. Didn’t work
-
There isn’t another functioning wallet still?
-
Broadcasting counterparty transaction…
-
So the answer is there are no working wallets. Got it. Thanks
-
-
So multiple bugs have been discovered with v10.x.y since it was released last week, including a problem with triggering dispensers via the API. It turns out that no one tested it for the ~month that it was in pre-release. I expected this to happen, and I warned everyone with a pinned message (see below). In addition, Freewallet has not been updated to use SSL for api.counterparty.io by default, so for now it won't work until you manually change the wallet settings. A new release is being prepared that fixes all known regressions, and I'll deploy that to the public API servers as soon as it's ready. In the meantime, if you would like to use v9.61.3 on plain HTTP, which is insecure, just hit http://api1.counterparty.io:4000. (In Freewallet, set "CP Host" to "api1.counterparty.io" and "CP SSL" back to "No".)
-
-
-
-
It will all be fine —- we are in good hands 🙏👍💪💎💎💎
-
Da
-
Simple solution: sneaker-net.
-
Periodic scammer alert.
There’s a fake scammer RarePepeTrader around again.
If you click @RarePepeTrader you get me.
Any other account is not me. -
They’re a lot rarer when we cannot trade them :)
-
I’m considering opening an IOU market. I will manage a digital resource to manage IOUs. No need to use counterparty.
-
How are your clay tablet baking skills?
-
I’m thinking an Excel sheet
-
I have no problem sending tokens on the network with Freewallet, as long as I simply enable SSL in the settings.
-
@teysol please post a screenshot of your freewallet settings page.
-
-
yeah I mean idk what to say. There's a three-year old outstanding issue that is surfacing more frequently now. There's no shortcut, folks: the source of this issue, which has existed for three years, needs to be discovered and fixed.
-
@misterwheeler was this for dispensers or a diffferent tx type?
-
-
-
-
-
Kek
-
@teysol is dealing with this as we speak.
-
-
the issue has not been solved in the 7 minutes since you surfaced it. appreciate your patience.
-
ah its ok no prob 😆ty
-
Was happening all day yesterday too. Standing by for fix as well.
Super grateful for what you guys are doing! Big things coming for CP 🪖🐸✊ -
-
can you provide steps to reproduce?
-
was this for dispensers or any tx type?
-
-
-
got it, okay tyvm!
-
looking into it
-
-
Issue Broadcasting Transactions?? · Issue #1656 · CounterpartyXCP/counterparty-core
I have no idea what this is.
-
i don't use freewallet but presumably if you open up the console it'll have the raw tx? any help there would be appreciated.
-
-
Lemme see.
I'll ask -
See the message pinned in the channel 👆
-
-
YES I DO
-
I Does it but show the error
-
can you please post your freewallet configuration page?
-
-
thank you.
-
Users did not get any type of courtesy when numerics were yeeted out of freewallet and xchain. Easy with the drama.
-
Good grief, Jeremy
-
-
-
Before v10 the test suite was broken for over half a decade, and the checkpoints (which are the only way of knowing whether consensus hasn't been broken) hadn't been updated for 8 years. With those things fixed it's perfectly reasonable to expect users to test software during the release process... that's what the release process is for.
-
? Did you think Adam said this as some sort of weird empty threat or for his own amusement? https://t.me/Counterparty_Dev/12081Adam in Official Counterparty Dev 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.
-
Seems highly wallet and configuration related vs protocol related.
Freewallet is using two api’s. It seems that one is for getting balances and info while another is for transacting. Ideally, and hopefully soon, users could change API’s in freewallet and regain access to stamps and numerics too. -
-
-
-
yeah there is no reason to whitewash this: there are some stability issues. They're being dealt with, but they're there.
-
-
the upgrade to v10.x.y was *not* mandatory, but running v9.61.z at this point is questionable, to say the least, given the numerous known consensus issues present in those versions. the public API servers that I'm hosting (at api.counterparty.io) are thus running on v10.x.y, which wasn't tested by the community at all before the release
-
There are a few known issues at this point. (most significantly, triggering a dispenser is broken at the API level 😔) but we're working on fixing that right now. Otherwise, it would be very helpful if bug reports were filed, with logs + steps to reproduce, so that we can get all of the kinks worked out straight away
-
(We still don't have steps to reproduce this issue in particular:
https://github.com/CounterpartyXCP/counterparty-core/issues/1656)Issue Broadcasting Transactions?? · Issue #1656 · CounterpartyXCP/counterparty-coreI have no idea what this is.
-
If we scare off these devs there probably won't be any new ones 😅
-
-
It's not only about new ones (that will definitely be hard to see happening) but also about having the original team putting the work into counterparty. All the support on the work being done 🫶
-
should we switch back from the coin daddy settings?
-
Nobody gives a shit about those 🤣
-
Just an asset send
-
Unfortunately it's hard to say right now. It depends on what your use case is. CoinDaddy should work well however
-
Just to send an asset
-
I feel like this is the heart of the issue
-
What wallet are the devs using for testing? I need that wallet bc at least it works
-
rarepepewallet works fine, what are you trying to use it for?
-
-
-
-
-
-
ty i will to try
-
@teysol what server are you using
-
-
I have a question about API performance with v10 - should I ask here or in the Dev group?
-
it seems like it fell
-
nop, my bad
-
I think the dev group is better, but up to you!
-
so you were able to do a dispense?
-
https://xchain.io/tx/dae81eb29cec819c600223389500e37b0701aa2e00a919747275a0c285f3eba5
Look how is in process I think -
-
yep, looks good!
-
-
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.
- 15 April 2024 (63 messages)
-
-
Can you please be more specific? What action did you take (specific values, etc.)? What was the expected outcome? What was the actual outcome? Screenshots, logs, and so on, please
-
do you have a tx hash?
-
-
-
-
-
-
-
-
this is for the dispenser, not your tx. do you have a tx hash for the dispense you triggered?
-
-
Bitcoin Transaction: 0f280d2a142950d697ba9339da635e30e40522cb82d56d3b8728acb2839186cd
Explore the full Bitcoin ecosystem with mempool.space
-
-
that looks like a txhash yrp
-
one sec
-
-
-
looks fine. dispense appear to be triggered and dispenser is closing
-
please share the xcp tx hash
-
(for unconfirmed dispenses I've sometimes seen xchain not pick up txs. would recommend memepool.wtf in those cases.)
-
tx fees are crazy ATM! looks like yours will be stuck in the mempool a while yet.
-
@Arvik78 bumping this. signing off pretty soon. if I don't hear from you will assume everything is fine.
-
-
I am not familiar with freewallet's workflows, sorry. perhaps someone else can weigh in.
-
-
-
-
looks fine. everything looks good. dispenses are triggered and dispensed amount and remaining quantity are as expected. Your txs are just unconfirmed because transaction fees are nuts.
-
-
awesome.
-
-
-
this is an inherent limitation of dispensers
-
you can be front-run
-
but in this case the important thing is the protocol is working as expected.
-
in the future if you want to check your unconfirmed txs, go to mempool.space, put in your address, and paste any and all unconfirmed txs into memepool.wtf
-
-
into memepool.wtf? not sure but don't think so. think it only accepts blocks and txids
-
okay all known regressions in v10 have now been fixed and redeployed to api.counterparty.io except for:
* A problem communicating with AddrIndexRs that causes nodes to fall behind temporarily (https://github.com/CounterpartyXCP/counterparty-core/issues/1663)
* A possible issue with broadcasting valid transactions that we haven't been able to reproduce yet (https://github.com/CounterpartyXCP/counterparty-core/issues/1656)
While we're fixing the former issue, the availability for api.counterparty.io will be intermittent. If they don't work for you immediately, try again in a few minutes. -
Thank you so much for all the hard work and great communication 👍🙏
-
You guys are savages!! Thanks ya Big time 🪖✊
-
-
Hi @teysol
I have a second computer with freewallet. And i received the same error.
So I setup the CP SSL to yes like you explained to me, but it's not working (I updated my version today, after uninstall / new install) but I am still receiving the error api counterparty
So I tried to modify my setting to switch to coindaddy like jdog explained. The transaction finally broadcast fine.
How can I do to setup again counterparty without any error please?
Thanks for the help :) -
please post a screenshot of your freewallet config
-
-
Hi ^^
with these settings the transactions finally broadcast. But I want to switch back to counterparty server -
please try switching CP Host to api.counterparty.io
-
and CP Pass to rpc
-
oof and the port to 4000
-
-
not anymore the api error but having this.
-
-
What the psswd for testnet when back to api counterparty?
-
rpc
-
did you happen to capture the logs when you got this error? never seen this one before
-
-
was a bad merge somewhere: https://github.com/CounterpartyXCP/counterparty-core/pull/1672add undefined error class by mattmarcello · Pull Request #1672 · CounterpartyXCP/counterparty-core
Counterparty Protocol Reference Implementation. Contribute to CounterpartyXCP/counterparty-core development by creating an account on GitHub.
-
-
Thanks! However I'm still getting some (intermittent) connection failures
FYI this was 2 min ago:
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\" }"
upstream connect error or disconnect/reset before headers. reset reason: remote connection failure, transport failure reason: delayed connect error: 111 -
-
-
Yep, looks good! Thanks 👍
- 16 April 2024 (18 messages)
-
-
-
Updated - 7046 XCP available on verified dispensers
https://xchain.io/tx/876b0bd18141903037de3763c898418b7f053511144af90b3106f477cf71931a -- 0.00017850 -- 365 XCP
https://xchain.io/tx/23bccae79a5c2a58cd1f205ebe099e99c0d0a81f813c7496335ba0ce9eae5174 -- 0.00018000 -- 498 XCP
https://xchain.io/tx/d4ff644f16f54779e25bec6ad80150373e1a26c42ab8709bad100d9272692dd4 -- 0.00020885 -- 1825 XCP
https://xchain.io/tx/86dfd890e6bb300588c70f97cf506766f0da4bc58acde8228e78e33f4e1e7637 -- 0.00020900 -- 201 XCP
https://xchain.io/tx/22deea485b5a76cc40cc1c0cb1e51f86fbd6ec75053acb532f15773a66f8e2ba -- 0.00021950 -- 300 XCP
https://xchain.io/tx/8341a8a21a30ea3e294dff97ef56849962eec92a3c2b82eb1c89372d78b9c5f4 -- 0.00022000 -- 94 XCP
https://xchain.io/tx/65f367cd9628d4bf9888741c0eb83fb078863029fc6af8178b673f26ded75c85 -- 0.00022800 -- 246 XCP
https://xchain.io/tx/ff299c8face1fe73c34fc3fce39a4d1182b496d53b940ecbdb3612dfa657a267 -- 0.00023000 -- 234 XCP
https://xchain.io/tx/852277eeda9a25194d9c09650193da474eb2600995ee968d8f70e45892b0fdf7 -- 0.00023300 -- 250 XCP
https://xchain.io/tx/5eebfadb25430a7aa6439ded6be53ebf0303b783045e8ca4091b4c246c346b08 -- 0.00024000 -- 874 XCP
https://xchain.io/tx/629f0a2001d763d976316ce4adfbfc8e852096b920cbf0ab778b53618abb3a7a -- 0.00024690 -- 1791 XCP
https://xchain.io/tx/889bd140dae2f07d28494ce7409475bf63c0deff09f50293d9ad05f5f752ee72 -- 0.00029999 -- 370 XCP
- As always just DM me if any questions or issues with these dispensers -
Hi,
I am having it now again :( Do you need more information please? -
-
-
Gm sir, I sent btc from my wallet to other btc wallet and it was valid but didn’t receive the btc yet
-
-
Okay 🙏 thank
-
will counterparty join token2049?
-
-
Ask here: https://t.me/freewallet_ioFreewallet.io Chat
This is a channel to discuss FreeWallet and ask questions and let the community answer
-
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...
-
-
-
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...
-
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
- 17 April 2024 (16 messages)
-
Wts ETHEREUMCARD
-
Any intentions of psbt trading on stamps/src20 tokens? Seems like easy way to completely dominate runes narrative
-
Not easy from tech side of course. I’m just a simpleton. Just confused as to why people are so excited about brc20 migrating to Solana or bridging to runes when this stuff exists in stamps already
-
because beside the OGs behind the runes protocol it is also a sell news + 2nd largest nft collection worldwide
-
Yea makes sense. I get it’s narrative chasing. No action I’m patient. How are runes in any way technically superior to stamps?
-
It’s on the Counterparty roadmap. Fingers crossed
-
Yup, PSBT support will be added as part of v10.1.2: https://github.com/CounterpartyXCP/counterparty-core/milestone/17
Atomic swaps are pretty much "the" feature at the end of the current roadmap. There's no issue yet and I don't want to speak out of turn but I think they'll be part of a release incorporating other protocol changes: https://github.com/CounterpartyXCP/counterparty-core/milestone/18v10.1.2 (API v2) Milestone · CounterpartyXCP/counterparty-coreCounterparty Protocol Reference Implementation. Contribute to CounterpartyXCP/counterparty-core development by creating an account on GitHub.
-
NB SRC20 will not work with atomic swaps.
-
They aren't Counterparty, agreed. That doesn't preclude the possibility of atomic swaps being implemented independently of the CP solution.
-
oh for sure, didn't mean to imply SRC20 *can't* implement atomic swaps, but as a non-CP asset it'll have to be implemented by that network's maintainers.
-
If you had to ballpark it (which I know is difficult and contingent on a lot of unknowns) how far out is atomic swaps? Early 2025? later?
-
sooner for sure
-
That's great to hear!
-
It'll be the next thing worked on as soon as addrindexrs is killed
-
-
👋 hey, anyone able to send some testnet btc? tb1qu028sleqeugup5gzxj7wsvhenqtuw02g3yqxfc
- 18 April 2024 (81 messages)
-
-
Freewallet (freewallet.io) supports BIP39 and Counterwallet passphrases... (dont know if Counterwallet used XCP BIP32 though)
-
is Counterwallet not in existance anymore though ?
-
I believe a protocol-level issue broke Counterblock (and by extension Counterwallet) late last year: https://github.com/CounterpartyXCP/counterparty-core/issues/1294
Beyond that I believe that Counterblock takes minutes to parse blocks and is thus untenably slow.
We're working on getting Counterwallet back up but AFAIK there is no functional wallet that supports BIP32 atm.Issue with v9.61 in counterwallet+counterblock · Issue #1294 · CounterpartyXCP/counterparty-coreFrom @jdogresorg in a chat: """ For the past week or so counterwallet has been down because counterblock (counterwallets backend) has been choking on parsing blocks. There is a probl...
-
-
-
-
-
-
-
-
-
-
especially FW, if you get rate limited the balances, orders or just anything else would not load and people might think they got hacked, lost assets or other reasons of why is that happening. when you get limited it doesnt say you got limited, it just simply makes your balances incorrect. this is the worst of what wallet could do - to confuse its users and cause stress
-
-
as example, if i had 20 address'es on FW and i knew one of those address'es hold nakamoto card let say.
What would i do is i would try to open every address and find where the card is. but a little problem is that if i wouldn't open the correct address from few tries, the rest will be shown as empty even if they had a card just because i could have been rate limited at some point of clicking and they would reflect me empty balance when its not. -
-
-
-
-
But I can't use the menominc I have on free wallet
-
-
it's rate limited because of previous over API usage
-
could help with that
-
I think indiesquare used BIP32, that's what I saw in some posts
-
-
-
-
-
-
-
-
-
-
-
-
-
no need that
-
-
-
-
-
-
-
Hi, I’m a representative from Web3 Global, looking to discuss with someone from the team regarding events and free/mutual partnerships. Who's the go-to?
-
This would be a huge upgrade. New indexer. Yea? Seems like that's one way to get DEX prepared
-
Atomic swaps != dex. Counterparty's had a dex since it launched more than a decade ago. Not sure whether SRC20 has one.
-
we dont need version v10++ to implement atomic swaps, atomicswaps are just a PSBt with a coordinator .
-
_trustless_ atomic swaps are different.
-
🙃😁
-
Atomic swaps in theory are trustless.
-
Whether HTLC or PSBt in definition they are decentralized trades without trust
-
PSBT Support via attaching assets to UTXOs · CounterpartyXCP/cips · Discussion #134
CIP: XXX Title: PSBT Support via attaching assets to UTXOs Author: Derp Herpenstein Discussions-To: ?? Status: Draft Type: ?? Created: 2024-1-26 Definitions PSBT - Partially signed bitcoin transact...
-
hi im holding satoshicard on eth emblem
how can i transfer it back to xcp and list on dex? -
go to emblem.finance, log-in and crack the vault open. This will expose the private key which you can then import to freewallet
-
thanks!
-
pepe.wtf (@pepe__wtf) on X
🐸Pepe Pawn Shop is pleased to announce the upcoming sale of one of the most coveted Rare Pepes in existence, PEPETRATION!🐸 DETAILS: WHEN: 4/20 at 4:20pm UTC WHERE: https://t.co/5tHhFOvlax PRICE: .69e or btc equivalent Only 69 available! See next tweet for more info!
-
-
Yep, not even close to that 😭😂
-
-
-
-
I wish people could buy advertising space on the homepage using a token
-
Has that troll ever offered anything useful 🤣
-
-
If I could create a dispenser, send the xchain feature token to the dispenser and it puts it front and center for X amount of time
-
Try xcp.dev, it features non-paginated results
-
-
I’ve seen some interesting broadcasts lol
-
fantastic! ty sir. mobile free wallet is my ideal mobile wallet rn
-
do you know if it supports the authparty method? rarepewallet.wtf I mean. https://gist.github.com/jdogresorg/782d697c610f543ad0d7da615160a4b2Description of Authparty authentication scheme which extends the counterparty: url scheme to support actions and callbacks
Description of Authparty authentication scheme which extends the counterparty: url scheme to support actions and callbacks - QR_Authorization.spec.md
-
-
Yeah, that's the fall back option. click login is pretty nice tho
-
https://t.me/Counterparty_XCP/226293 Did you forget that my assets survived the drama while others referenced dead JSON? You even asked me for help with your TG bot that still doesn’t work. I’ve done nothing but speak the truth. Hate hate hate, nbd.
-
-
My tg bot works perfectly thank you
-
where are you trying to log in?
-
is the old rpc api now unavailable? I tried accessing using the updated v1 4100 port but it doesn't respond
-
pretty sure it's 4000...
-
Oh good! Building something that used it. But not sure how the ux would work, since it is not an app
-
that's for the v2 api no? I am basically trying to keep my old code (using rpc) working while i am migrating
- 19 April 2024 (55 messages)
-
rpc api available on port 4000
-
V2 api isn’t released yet
-
Descifra el futuro de Blockchain con expertos | Blocklack Space
Descubre las tendencias y predicciones del futuro de Blockchain con expertos en nuestro evento en persona en Blocklack Space.
-
pepe.wtf (@pepe__wtf) on X
🐸Pepe Pawn Shop is pleased to announce the upcoming sale of one of the most coveted Rare Pepes in existence, PEPETRATION!🐸 DETAILS: WHEN: 4/20 at 4:20pm UTC WHERE: https://t.co/5tHhFOvlax PRICE: .69e or btc equivalent Only 69 available! See next tweet for more info!
-
~~ANN New Release of Counterparty Core~~
https://github.com/CounterpartyXCP/counterparty-core/releases/tag/v10.1.1
This is a relatively small release with a number of bugfixes, one of which is critical—there is a bug in previous versions of v10 that can cause nodes to crash after a blockchain reorganization.Release v10.1.1 · CounterpartyXCP/counterparty-coreRelease Notes - Counterparty Core v10.1.1 (2024-04-19) This is a relatively small release with a number of bugfixes, one of which is critical---in v10.0.x and v10.1.0 there is a bug which can cause...
-
@teysol has v10.1.1 been deployed to api.counterparty.io?
-
-
oh right, now that explains why it wasn't working 🙂 perfect thanks
-
Interesting network stats here:
https://www.xcp.io/chartsCounterparty AnalyticsDetailed insights into Counterparty.
-
where should i be pointing my CP HOST on freewallet? i keep getting time out errors
-
you upgrade to 0.9.31? jdog made the new version default to public.xchain.io in the recent release
-
-
depending on your version it could also be the SSL settings in testnet and main to be set to YES
-
ive been recently using api.counterparty.io and not been having issues myself - though havent tested in the past few days
-
yeah timeout errors with this are not normal and should be reported so we can fix them 🙏
-
thanks
-
just tested opening a dispenser with counterparty api and worked for me ❤️
-
@scrillaventura any further issues?
-
-
It’s timing out quite a bit still but I got it working
-
following up in DM
-
-
-
-
-
Can you please share your "Settings" page?
-
-
At the bottom of the screenshot you posted it says "Settings"
-
click that and post a screenshot
-
-
please try updating your settings to match this screenshot.
-
-
-
Okay we got some reports of this after the release of v10 last week but haven't gotten such a report since then. Will look into it ASAP.
It looks like you're using the mobile freewallet. Can you please try using the desktop app, change your settings as I described and see if you get the same issue? -
-
-
-
I am sorry I can't help further. Perhaps something in @davesta's freewallet user manual can help: https://davestaxcp.gitbook.io/freewallet.io-user-manual
-
keep in mind I am still in the process of updating (and editing) this user manual at the moment - but there is alot of good information there for new users
-
your best bet is to use the most updated version of Freewallet DESKTOP version which is 0.9.31
the Mobile app has not been updated since 2019 -
-
you can mint with rarepepewallet.wtf which is Joe Looney's new browser wallet... minted one today using it (might bump the fees up higher though with this unpredictable mempool)
-
Rarepepewallet.wtf
It does auto IFPS
Just upload image in wallet and issue the asset. -
the auto IPFS is SO freaking nice
-
-
Is it safe to import my old passphrases into this wallet?
-
It is a browser wallet so it has its own risks, so best to wait till you can use Freewallet Desktop...
But when it comes to security. Joe Looney is one the most if not the most respected devs in the space when it comes to wallets...
I'm also pretty sure rpw is open source on GitHub too if you'd like to review the code -
-
Yea, I'm playing around with it now. Doesn't seem to give me access to all the addresses that I have in freewallet for the same passphrase
-
I believe you can change addresses near the top with the button with "two arrows" ... But haven't clicked around too much yet on that wallet
-
-
-
Thanks
-
-
- 20 April 2024 (32 messages)
-
-
What is tesnet sir?
-
Yest tesnet
-
Look at the scrow and remaining.
-
Does this mean it is not real xcp
-
I think is a underflow bug
-
-
Sorry is justs a dispenser refill
-
Can I buy from this penser ?
-
Is just testnet, not value...
-
-
$100+ tx fees 🤯
-
Will probably stay this way for the entire day (Runes launch by Casey Rodarmor)
-
weren't they $50 around the time of this incredibly moving interview (/s)?
-
-
-
Every cycle every year every day, crypto never stops 🔥
-
This is top testing.
-
-
-
Less than 2 hours til PEPETRATION is live on pepe.wtf/drops!!!Drops | Pepe.wtf
Discover the universe of Rare Pepes
-