Getting closer and closer to just saying fuckit and just supporting Counterparty Classic in FreeWallet and dropping support for CP 2.0 entirely 🤷️️️️️️

That would be a real loss, freewallet is the only fully featured wallet. I'd definintely understand though

I love FreeWallet it’s really good

Only wallet I’ve ever really used for counterparty

Not there yet... will just fix the tx signing and put out a new freewallet release and get things working again... but this cat and mouse blame game is really tiresome... and distracting from me working on xchain platform, which is where I think things will be going in the future

I don't think this is correct because the API host is wrong. @jdogresorg know you're scrambling but just post a screenshot of the XCP api settings if it works on your end... So we can copy word for word exactly what needs to go in every input

This is what he sent me lol

right now, regardless of what API you use, you will be unable to sign the tx in freewallet... if you HAVE to do a send now, prolly best to use horizon... Javier is digging into why freewallet is having issues signing (it signs using the old counterwallet code)... i'll put out a freewallet release once this issue is fixed... it is top priority

also the CP 2.0 API is consistently crashing here on tokenscan... and no support or help from the cp 2.0 devs.. so, will focus on that issue after the signing issue is fixed

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

Created an issue reporting the issues I am having to the core devs in the "official" way.... now we wait to see what they respond with.

an idea for the type of people we are dealing with

Not even bitching about removal of addrindexrs... just trying to stand up a single counterparty-core node, just like any new user would... its always personal with them it seems 🤷️️

Well, we did get a meme...as i predicted

Issue says clean install was done to 10.9.1 - instructions for node operating was first update to 10.9.0 then move forward to 10.9.1

Yeah... I did a brand new clean install of 10.9.1... if one is supposed to "upgrade" to 10.9.0 first... where are the instructions on how to do that? only instructions I see on "upgrading" are on this page https://docs.counterparty.io/docs/basics/getting-started/ which says to

`cd counterparty-core
git pull
docker compose stop counterparty-core
docker compose --profile mainnet up -d`

which is exactly what was done

they say "upgrade to X first"... and yet, no instructions on how to do so other than the general upgrade instructions are given... release notes dont say shit about what to run to "upgrade"... hence just went with what was on the website... and as I said, I did a clean install of 10.9.1

removed all dockers and images

the tokenscan API is back up now... and Javier is working on a PR to get signing working again (its related to the CP API no longer passing the input script)... We just need to decode the tx and determine the input script type before signing now... should be fixed in a new release momentarily

public.tokenscan.io

running on counterparty-core 10.9.0 right now, as that version seems stable and 10.9.1 seems to go into a crash loop... so sticking to 10.9.0 for right now

ok, confirmed, the problem is, they don't give the input script anymore

this is with their new api

this is with the classic api

can you tell the difference?

so, the only thing we need to do is to retrieve the transaction and copy the script

so, definitely, this is NOT backwards compatible

best solution: change the function signTransaction to decode the input(s) and find the scripts for those inputs

It's a Vector.
Frog army is Fukin shit up.

Hey frens!
I'm in the process of buying multiple assets from someone directly (no dispensers involved).
He currently only has the FW app on his phone, and is clueless on how to send assets from FW - much less multiple assets.
I've only purchased assets, never sent any yet.
Could someone please point me in the right direction to make this multi-asset deal happen smoothly and as inexpensively (fee-wise) as possible.
Thank you!

Check the User Manual ^ - learn what the Counterparty Decentralized Exchange is, what Dispensers are and how they are used (in a trust-less manner)

and it is recommended for both parties to use the most recent version of Freewallet Desktop Version, will make it easier for both of you (and dispensers only work right now with the Desktop version for both buyer and seller)

Does this mean now you get a raw transaction from the API thats not raw anymore because it needs further processing because its not just signable anymore in this "raw" state?

Yup, need to request the raw tx from bitcoind now cuz the cp api is no longer passing all the same info it did before

Yeah, the new counterparty API doesn’t hand back information that it used to in the transaction so FreeWallet is unable to determine the input types and hence is unable to sign…. As I said just a little while ago, you’ll need to wait for a FreeWallet update.

Javier is working on a PR with a fix for FreeWallet, and I have also asked Adam in the counterparty channel about why this information is missing and pointing out that it is not “backwards compatible” as the release notes indicate

Maybe a rollback is in order, and we just cut off the cancer that is 2.0?

Adam just clarified that the changes are due to something that he considers a bug…. Much like he considered origin functionality in dispensers a bug.🙄🤷🏻‍♂️

In any case, I’ll be putting out a new version of FreeWallet shortly which will address this issue , and allow transactions generated by the new counterparty API to be signed in FreeWallet

If anyone is interested in xcp assets on affordable budget prices.You can send a dm .