- 01 July 2025 (9 messages)
-
Love that one !! -
Oh my gawd sounds like me lol 😂 got to slow down lol 😂
-
Love it !!
I see it’s been updated lovely ! 🥰 -
Holy frog this is bad ass! -
1Lhoi43wAkTgei1WK5drpSF9V8Y76jnj89 -
Good day @jdogresorg. When you have a moment, can you force a reload of the commoncoco project json? The last 5 tokens I added are not showing the green banner. 1 was 2 weeks ago and the other 4 were about an hour ago.
Thank you! -
fixed - 02 July 2025 (24 messages)
-
138kNmWCdJxGUGUxMzgcjMpHVhqGaDrh1k -
13j9aWM7hAJCgpFq2uWPUtJ36ZiCX139DG thank you -
17Xw41Zg2zxNV5DcCPQ28TdSVaAwk1SpdA -
-
1BH9sBVQ645gx2D3pfkc95SSvvEXpFhw2N -
bc1qrtl9q2w5surqf6uu87rceqx7vf7k8vw2glfx5f ❤️ -
I had same problem yesterday with GAMESOFVANCE, i filled the description field during the issuance process and it shows nothing once created. Maybe there is a kind of latency with tokenscan? However i didn't want to wait too long so i made a desription update and it was allright after that.
-
Once a transaction is mined in a block and counterparty processes it then it should show up on token scan within a minute or two🤷🏻♂️
Thanks for the heads up. Please let me know if you continue to experience this issue. -
Thanks JDog, in my case nothing happened, I let 1h and then I did the update with another transaction & it was allright
-
For instance this one (it's not mine) is not showing https://tokenscan.io/asset/A6456997157481204000, despite there was a description in the issuance https://tokenscan.io/tx/3035234
-
If you look at the token that you sent me and then look at the issuance is for that token you will see that they were two token issuance one had an asset description, and the most recent one had no asset description set…. Which is why the asset shows no description because the most recent asset issuance did not have an asset description set.
If you’re saying that something looks off, please check the most recent issuance is and verify that there is indeed an issue ….. the asset description always reflects the latest asset issuance information, and in this instance when I checked the latest asset issuance, there is no asset description set….. hint token skin is showing the correct information -
The latest issuance for the token that you linked is actually this issuance
https://tokenscan.io/tx/3035316
Which you can see does not include an asset description, therefore the asset description is blank.
If you run into a case where the latest asset issuance shows a description, but the token itself does not show a description. Then I would say that there is an issue…. But what I have seen in the last two examples that people have brought forward is that they did issuance is where the asset description was blank, which explains why the asset description itself is blank….. the asset description always reflects whatever data was in the last issuance -
In the step by step instructions it does walk you through adding the JSON file first (description) and then later updating the token amount. Maybe that’s what’s confusing the process if folks are used to doing steps in that order? And the amount issuance is ‘blowing out’ the description? -
you're probably right, i don'ts know what Simon did exactly.
As for my case, i issued a token with description
https://tokenscan.io/tx/3036197
and then description disapeared, maybe when i locked the tocken after creation ?
https://tokenscan.io/tx/3036201
then i made a change of description and it was ok
https://tokenscan.io/tx/3036243 -
I think it is related to doing two issuances at once... if you do one issuance, then wait for it to settle into a transaction and THEN do the next issuance... all should be fine
-
what is happening is most likely... token has no asset description.. users do issuance with token description set, but BEFORE that transaction is mined, they issue some supply... the "issue supply" form just passes forward the existing asset description... and since ppl aren't waiting for the first tx to settle in a block before doing the "issue supply"... the "issue supply" is just passing forward the blank asset description
-
I think part of the issue is in freewallet the issue and change description are separate actions.... but in reality, both could be done in a single transaction if I had forms which allowed it....
-
if you could create an issue on github at https://github.com/jdogresorg/freewallet-desktop/issues ... then I will have it on my todo list to look into it the next time I update wallet.... either by creating a single form to update both supply and descritpion at once.... or (more likely)... to check for a pending issuance and set the asset description to the pending issuance description instead of the CURRENt issuance description.... in this way users could do what your trying to do, change asset description and do token issuance in 2 separate txs without having the second issue supply tx blow away asset descriptionjdogresorg/freewallet-desktop
Desktop wallet for Win/Mac/Linux which supports Bitcoin and Counterparty - jdogresorg/freewallet-desktop
-
as always... thanks for reporting your issues and working with me to try and figure out WTF is going on... 99.9% sure it is just a case of doing 2 issuances at once..... prolly best to do one issuance, then wait for it to settle in a block, then do second tx.... should fix the issue in the short-term 🙂
-
Description is deleted in lock tx · Issue #257 · jdogresorg/freewallet-desktopWhen I Locked asset XRAYPEPE's Issuance with freewallet in a second transaction after the Create Token tx, it deleted the description json in the lock issuance tx so all images would not show i...
-
-
-
Interesting! This in the UI would be so nice -
Alright frens, I just sent them off Thanks for all your help and feedback
- 05 July 2025 (5 messages)
-
Still the most functional wallet I own -
a lil info on the 2 issuances at once 👉 i created an asset 5 months ago and i used the json (obvi cost a lil more since its more data). i decided to sub it to a directory (cant say which one but you can prob guess lol). so i needed to lock it. after i locked it, the descrip was gone on tokenscan/horizon/xcp dot io.
in this situation there was a 5 month difference between the issuances -
only solution that worked was to reissue the description using the EA link instead of the json. it worked so i could sub the asset but obvi id prefer to have the json. and not have to reissue. hope this helps
-
yep... will look into it next week... seems that the latest counterparty update changed the way that asset descriptions are handled and now users have to pass forward the asset description with each issuance (which makes them unnecessarily more expensive, and is the reason why Javier and I added the ability to pass null for description and have the description carried forward.... guessing this is yet another case of the counterparty-core devs "fixing" something what was a feature, and now making things more difficult and expensive for the end users..... An issue has been created for this on github... please feel free to leave your feedback on this issue and i'll get to it ASAP
-
Description is deleted in lock tx · Issue #257 · jdogresorg/freewallet-desktop
When I Locked asset XRAYPEPE's Issuance with freewallet in a second transaction after the Create Token tx, it deleted the description json in the lock issuance tx so all images would not show i...
- 06 July 2025 (1 messages)
-
1EAECn7nzqMbk7FD3qa1dvbYkWj58iSV69 - 07 July 2025 (50 messages)
-
I have an asset (WEALTHPOT )that has not been showing the big picture on tokenscan,I've changed the description several times but still not showing...do you have any idea on what may be the cause ?The description and every other detail is perfect but still not displaying the big picture..
-
Gm sir, I just mint and used permanent arweaving but after some additional fees still it’s doesn’t create the token assest and I try to used short description and it work but currently it doesn’t show my descriptions I’m just curious before mint the second one sir any assistance
https://tokenscan.io/asset/LFGQUEEN -
Just read the few messages above, when you locked the asset you lost the description. Use the function „change description“ in freewallet for example and paste the json one more time then you will be good.🍃
-
Do you mean I will need to change once again 🤔
-
Yes
-
Okay will try that thanks you sir 🙌
-
hrm looks like you have a description but the asset is still not showing... will look into this
-
looked into it... your card is a part of a project "Faux SOGs"... when a card is a part of a project the image that is shown is driven by the project and the project JSON.... so that when you submit a card to the project, it shows the card that was approved by the project and your not able to change the project image after it is approved.... in your case, the project JSON does not show the correct URL to your image
-
-
-
in your case the project faux sogs has a bad URL for your card image which is why it is not showing up\
-
get in contact with the Faux SOG project, tell them to fix their JSON to point to a valid image (drop the extra ;WEALTHPOT on the end of the image) and then have them tell me when it is fixed and i'll reparse their file
-
this is not a case of you doing something wrong, but rather a case of the faux sog project not using the proper image link to the card image
-
Ok thanks
-
Have been minting another assets now but it only debit liquidity and no assets was creating
-
debit liquidity and not assets was creating... not sure what that means
-
if your having an issue, log the full details of exactly what your trying to do and include links to transactions so that it is easy to figure out what your talking about
-
pretty sure the latest 11.0.1 update changed issuances a bit more than they let on.... so will need details to look into it
-
I noticed that after minting and locking an asset the description disappeared,so I had to re input the description again before it was okay ...
-
Exactly my point, thanks you for the heads up 🙏
-
yes, that issue has been discussed here a couple times and an issue has been created
-
Sir I decided to used normal description and will change it later like first one thanks 🙏
-
Someone impersonated you sir
-
-
Thanks for the info... the scammer has been blocked from this channel... hate scammers
-
Thanks I will change the description once again like the previous one 🙏🥰
-
Ok no p
-
trying to burn token and having an issue... is this a known thing or should i reconfigure my hootinanny?
-
trying to burn a token? you cant burn a token... you can only 'destroy' a token
-
what problem are you having? details pls
-
trying to destroy some pepe cash
-
i hit the button but nothing happens
-
tried closing wallet and restarting it, and tried making sure im on the most current and it seems like i am
-
Unplug it and plug it back in -
not discounting pilot error
-
im sure its me
-
-
YOOOOOO... lmaoooo
-
scammer J dog did NOT see that coming
-
LMAOOOOOOOO
-
that motherfucker RAN lmaooooo
-
he RAN out of my DM's
-
so i had someone else try to destroy it and it aint work
-
lolol
-
so destroy function is not working now either? was a tx generated and just never decoded into a destroy on counterparty? could you pls create a github issue for it and i'll dig into it when I got some time... prolly later this week.. seems the latest counterparty-core release be fucking up on some stuff (undisclosed changes).... of course, i'm sure it is TOTALLY not intentional... TOTALLY not changes made to make my freewallet stop working and TOTALLY not changes that are integrated into horizon wallet and working fine 😛
-
not a problem
-
ahh the joys if conflict of interest and devs of "competing" wallet being in charge of protocol dev.... able to break shit that worked fine, then just shrug their shoulders and say "that must be a freewallet specific issue"
-
naww bro... freewallet didnt change... but nice try wankers 😛
-
jdogresorg/freewallet-desktop
Desktop wallet for Win/Mac/Linux which supports Bitcoin and Counterparty - jdogresorg/freewallet-desktop
-
file and issue for the destroy thing and next time i'm in updating freewallet i'll test the destroy functionality and see wtf is going on
- 08 July 2025 (42 messages)
-
-
Too funny
And familiar -
Awesomeness !!
-
Thanks Cody
-
Epic!!!! -
-
Love the dragon !!
-
-
xcp discussion live with Adam K right now
-
feel free to listen or join Jdog... but trying to patch up the communication with lead Dev and FW....
Adam mentioned if there was a "FW test suite" we could start testing new releases on some sort of process with FW.... instead of users manually doing individual things and finding bugs...
could there be a way to throw $50-$100 of btc at a mainnet "test" suite to do all functions in an easy way to make sure there arent bugs on new releases? (that arent backwards compatible with FW)
just trying build and come up with ideas to make the future a smoother process -
also as a side note... It seems obvious that since most of the community uses FW... When we will see Atomic Swaps supported within FW?
Id assume if it was supported and there was a "atomic swaps dex" tab in FW we would see much more usage for that function simply because most of us use FW as our main xcp wallet -
i'm not a big fan of atomic swaps, and there is no universal PSBT place where all devs can get a list of all PSBTs and do things in a universal way.... so, adding atomic swaps (and showing support for Adam's feature which are supposedly "better" than dispensers) is not high on my priority list
-
once I get xchain platform built... i'll circle back to Counterparty and see what needs updating, etc
-
understandable
-
but as of right now.. we have a ton of different marketplaces for atomic swaps (horizon marketplace, RPW, firemints.xyz, etc)... so because of how it was implemented, it can't easily be done in universal way.... sure I COULD add in atomic swap support... but it would only show atomic swaps which were listed in freewallet
-
would prefer to just do an end-run around all the marketplaces and just come up with a 3rd party component which allows for storing of PSBT without a fee.... then make it open for anyone to use it... then integrate it into freewallet.... that would make it so that ANY marketplace could get a list of all of the PSBTs that use the library..... and eventually, each of the marketplaces would migrate to using that...
-
why pay $2.00 to horizon to list shit in their walled garden or pay to list something in RPW when you can just do the listing for free in FreeWallet... tho, will take some dev time to build it all out, etc... and right now, my focus is elsewhere
-
how much organization would this need from all exchanges? Adam on the space mentioned "i think thats how ETH does it"... "they share market info"
where it be hosted? github or somethin? -
well it SHOULD have been built into the protocol.... and SHOULD have used XCP as a listing fee... but, Adam in his infinite wisdom determined he could extract funds from users by NOT adding it to the protocol and instead having each marketplace roll their own PSBT implementations..... as far as where would be it hosted... would prolly be something that could be hosted on github and updated every 24 hours... or even better, have the service integrated into the counterparty stack so that anyone could spin up a node and pull down the data and sync it each block
-
funny to me that adam makes all these changes and doesn't really understand how it works in the background.... in ETH, you delegate signing permissions to individual sites... so they dont have to keep track of a bunch of PSBTs like we need to on BTC.... things can just get listed for sale, listed in many marketplaces, and then when it comes time to actuall buy, the marketplace site just uses the permissions to sign the tx.... different model than PSBT
-
made it through 20 minutes of the interview... had to turn off cuz Adam's perception of things is so wild... that JP exploited a bug.... vs Adam and team changing 10 years of ledger hashes without any discussion.... or claiming that "nothing has changed in regard to asset descriptions".... but, FreeWallet hasn't been updated in 6+ months... so the only thing that DID change was counterparty... but, unless someone like myself is there to blatantly call him out on his bullshit, then he gets away with his talk-in-circles nonsense
-
yeah my main goal was to just keep the convo civil and ask q's to Adam without too much fighting - best to let the community hear his side of things .... but im def not the one to fight JPJA, yours, or Joe or anybody's fight
cannot stress enough its lucky we have any interest or even care to try to discuss things .... its work in of itself -
if we got into a yelling match no future convos would happen
-
couldnt agree more - even Kevin from stamps was against it rolling out that way
-
with that being said there was 25 other q's i wanted to ask - but woulda been there all day
-
yeah... taht is kinda why I decided to not participate... would be good to call Adam out... but in the grand scheme of things, he is in total control, and so its best to just let him do whatever the fuck he wants (he is going to do it anyway) and then there is no way for him to continue to blame his problems on me....
-
just wish other "taller" ... "pillars of the community" ask the real and direct questions . glad Shaban was there, def want to hear all the perspectives and how he responds to them.... probably less than 5% current active community there today
-
maybe i'll participate in the next one... but with my mental state right now, best to just focus on staying positive and building on xchain
-
too easy to get caught up in anger and frustration and get derailed
-
totally understand
-
Anyone figure out who it was that went off on Kane?
-
XCPGOD
-
Also.. funny to see that Adam blames the falloff of usage on counterparty on counterwallet breaking.... and that he said he tried to fix it for weeks.... which is weird... cuz, counterwallet works perfectly fine on counterwalletclassic.io and it took just commiting ONE of the 3 different fixes that Javier and I proposed years ago.... Adam wanted to kill off FreeWallet and Counterwallet and drive traffic to his wallets
-
-
-
also pretty funny that he flips blame around on the community and says "if you dont test the beta and report issues, that is not my fault".... hrm.. I thought that is what the test suite was for... to find issues BEFORE they are released in production.
-
def glad I wasn't on the AMA... I woulda been raging and it would have turned into a screaming match and not much progress would have been made.... at least this way others are being able to speak their mind and make their voices heard
-
we both know all voices must be heard though and the more qualified voices there are, the better the convo will be
bunch of topics I had to just let slide because I'm less qualified on...
also can't really dive deep on how Adam treated ZeroG on the GitHub when we are here now on a space
Happy to hear he regrets choices like destroying CIPs etc (wish you woulda heard us back THEN)
But yeah I know there's more to the story on CBOR, JPJA etc but I just simply ain't gonna stand in a battle I'm not the most qualified for. And either way, all we want is for all the pillars of the community to work together and find SOME sort of path forward that works
simply had to set some sort of example for dialogue so I don't have show up in the future I know at least the convo will still be going (sooooooo much more to discuss) 2hrs won't cut it when there's been 1.5 years of actions, comments etc etc -
u did a good job
-
was less soul sucking than arguing on tg ill say that lol
-
-
lol
- 09 July 2025 (2 messages)
-
Excellent job by adam and everyone else on that space. All makes sense to me as an app builder. -
... you are the kind of app builder working on an open source & decentralized project? You also mis/manage contributions and concerns from/of others who are developing for said app?
Maybe you have experience worth sharing with Adam so he can feel power rejecting your insight as well. If so, I expect censorship if you go slightly against the grain.
That's all I'll say about it here - 10 July 2025 (5 messages)
-
I exploited a bug LOL
I haven't listened to the interview but I did what I had to do after bei g ignored and my github issue had been blocked from github.
I simply used our permissionless platform the way it was designed. This effectively blocked Adam from rewriting history.
At first glance, what he wanted was simply to recover balances burned due to a dispenser bug. But..
1) Hashes changed back to 2014, long before the bug. What else was going on?
2) Even if hashes changed "only" back to the bug in 2017, it would be very difficult to verify no other changes happening (that's why hashes must never change )
3) Bug could have been used to burn. Very counterparty'ish thing to do. Unburning would change supply, thus value, a big NO NO.
If I having prevented this shit from happening by "exploiting a bug" i am happy i did. -
-
Trying to send corn with freewallet, should I wait it out or change something?
-
worked after 5th attempt.🙏
-
Make sure you’re on the default server settings…. If you continue to have issues, let me know. I’ll take a look at restarting the server
- 11 July 2025 (4 messages)
-
Is there a link how to fully uninstall freewallet
Or will a device always remember, with the password issues I've had, when I deleted it came back with the password issue -
click the "logout" button in freewallet, that blows away all the data saved in localStorage... then you can uninstall the wallet... uninstall just removes the application files, not the saved data.... clicking the logout button removes all the saved data... also.. what "password issues" you been having?
-
I mentioned before a few times, haven't happened again "touch wood", wouldn't let me log in, when input correct password did nothing, input wrong password (intentionally) says wrong password, started the process again on another device and happened a second time when I'd nearly sorted all the addresses out lol
-
Not sure why that happened, thought I did press logout but will try that, that makes sense, is nice to work off one device lol, thanks mate, will let u know how I get on
- 12 July 2025 (1 messages)
-
https://github.com/CounterpartyXCP/counterparty-core/issues/3196
protocol change - issue created in xcp coretoken lock resets description · Issue #3196 · CounterpartyXCP/counterparty-corerecent protocol change issue as seen with Freewallet 2.0.3 first logged: jdogresorg/freewallet-desktop#257 example tx: https://tokenscan.io/tx/3036866 counterparty-core/counterparty-core/counterpar...
- 14 July 2025 (1 messages)
-
- 16 July 2025 (13 messages)
-
If I may ask ,when will the mobile free wallet start working perfectly?right now can't send anything out from it ...
-
freewallet mobile has not been udpated for many years... this is nothing new... what is new is Adam and the Counterparty core devs changing transactions so that frewallet-mobile is no longer able to sign them... As far as when will the mobile wallet work again... when I have time and energy to focus on getting it working again.... right now my focus is on XChain platform, and usage on Counterparty is at all time lows, so not very high on my priority list to spend my time on updating a wallet for a platform which I no longer believe in, or see much future usage on...
-
Hopefully soemtime in the next few months after I finish working on XChain platform and xchain wallet
-
Ok
-
Desktop freewallet won’t let me send funds recently, I’m getting the insufficient funds message although I have lots of funds,
-
Check the error message... if it says "API Error" at the top of the error, that error message is comign directly from counterparty-core... and not freewallet (freewallet doesn't throw any insufficent funds message)... so prolly best to ask Adam and team about the error message... tho as soon as they hear "freewallet" they going to blame it on freewallet... most likely culprit is them replacing addrindexrs with electrum which is a 3rd party solution to manage utxos
-
could be all your btc is locked up in tiny dust amounts... dunno... but unfortunately I can't help with the "insufficient funds" message as that comes directly from the counterparty-core software, over which I have no control or power now.
-
Cheers man 😎👍
-
-
Blocked the loser
-
scammers gonna scam unfortunately
-
You can also try electrum ,just send the coins to your addy from electrum ..it will free your BTC
-
Thanks 👍
- 18 July 2025 (1 messages)
-
I had to use electrum..
- 23 July 2025 (3 messages)
-
Hi everyone!pls who owns this addy?
18kfuKxUXVLKU6apVyv2XwXa9kNvo58GzD -
?
-
I'm having a lil issue with the dispenser,it did not disbursed all I paid for
- 24 July 2025 (27 messages)
-
Lordkek for sale full card
-
-
Lots of pepes / nfts moving last few days..... we on the verge of nft season?
-
GM @jdogresorg. As you know, descriptions are now being wiped when locking an asset. Turns out it also gets wiped when transferring ownership. I know this is not your doing.
My question/problem is when trying to update a description while on a hardware wallet (trezor) the pop-up to interact with it never comes.
It does work when locking an asset and transferring ownership.
Any idea why some functions work with hardware and some do not? I realize I’m probably the only one doing it this way so not very high on your list -
probably related to how the data is being encoded... AFAIK hardware wallet stuff only works with signing from a single address, not with multisig signing
-
@teysol It seems that both Locking an asset AND transferring ownership of an asset cause the description field to be wiped. -
Yep, this is a known issue, and an unintentional regression in v11. The original Counterparty protocol required the description to be re-included in the transaction for all subsequent issuance transactions. At some point, a hacky workaround was put in place to skip this to save on tx fees. However this functionality wasn't documented or tested anywhere at all (as far as I know), and as part of adding Taproot support, we bypassed this logic and didn't realize it'd cause any problems (it shouldn't have). And because locking assets and transfering ownership re-use the issuance transaction type (🤮) the protocol understands those transactions as re-issuing the asset. There's an open GitHub issue to discuss the matter. In the meantime, wallet providers can update to re-include the description in these txs.
-
Adam great at passing the ball and avoiding blame at all costs.... calling the workaround hacky and such and saying it wasn't tested (actually, it was, cuz it worked fine).... so... to be clear, he broke stufff.. and his response is that wallet providers can make changes to force re-encoding of asset descriptions (forcing larger transactions and higher tx fees) rather than him getting off his ass and putting out a hotfix release
-
just want it clear what he is saying... trying to kick the problem down the line to wallet providers saying THEY can make a change since he broke things in the protocol... and also not mentioning that the change he wants wallet providers to make will make issuances considerably more expensive (having to re-encode asset description in every issuance... think about stamps use case... they now have to pay to "stamp" the asset description again and again every time they want to make a change
-
anyway... just needed to make it clear that once again, adam breaks shit, blames "hacky workarounds" (which worked perfectly fine), says testing didn't take place (he doesn't know wtf he is talking about cuz I personally tested every change to the code... something i WISH he did).. and then says that wallet providers can make the change instead of him fixing things quickly
-
Systematic destruction of counterparty n the Art in Facts..
-
All I know is everything used to work fine, and now it does not. I miss those days!
-
I wish those dudes would just fix stuff instead of writing a diatribe about the hows and whys
-
Meaning that if there is too much data for one op_return and there needs to be a bare multi sig created it's not going to work when using hardware?
-
I guess I'm going to need to sweep my wallet back to a hot software address and then move my grails back to the hardware wallet.
-
unfortunately that is probably best for now
-
testing stuff before making changes would also help... dunno what the "test suite" does that they keep talking about, but so far it hasn't found a bunch of changes and it is only AFTER they break things that they then become aware of the changes 😢️️️️️️
-
I have been following here for a long time. Are all the assets here experimental? -
xchain not been launched yet?right？
-
I remember minted some ＄gas token
-
xchain platform is still under development... yes GAS was minted a long time ago, and yes if you minted GAS you will get an airdrop of XCHAIN when the platform launches
-
this is a channel for discussion on freewallet desktop and items related to freewallet desktop... for discussions on BTNS go to @BTNS420 or for discussions on xchain platform go to @XChainPlatform
-
thanks dev
-
-
-
Probably yes -
- 25 July 2025 (2 messages)
-
This guy is an absolute tool -
Good thing the token is the art
- 26 July 2025 (12 messages)
-
One of the reasons the Philips head was revolutionary, 100 years ago, is that it has a self centering feature.
My vote is a screw driver, because that's the only action I see from his department
Didn't realize how much of a Swiss army knife freewallet is, until this last year -
man, that could be a freaking disaster for grails... hope they fix it -
I haven’t been keeping up, but I saw some people saying they couldn’t burn pepecash recently -
Was there another change that broke it?
-
yeah i finally filed a protocol issue for it rn
https://github.com/CounterpartyXCP/counterparty-core/issues/3199destroy function not issuing tx · Issue #3199 · CounterpartyXCP/counterparty-coreFreewallet v 2.0.3 multiple users reporting new protocol version is not accepting destroy function tx's FW chat Fake Rare chat bug filed in FW github: jdogresorg/freewallet-desktop#259 since pr...
-
furthermore Subterranean noticed that the reset description bug on locking assets ALSO exists when transferring Token Issuance Ownership.... which makes me weary that maybe Sweeps (with Token Issuance Ownerships moving) would also reset the description
https://github.com/CounterpartyXCP/counterparty-core/issues/3196token lock resets description · Issue #3196 · CounterpartyXCP/counterparty-corerecent protocol change issue as seen with Freewallet 2.0.3 first logged: jdogresorg/freewallet-desktop#257 example tx: https://tokenscan.io/tx/3036866 counterparty-core/counterparty-core/counterpar...
-
-
Probably… each sweep does result in an issuance so you might be right
-
Yeah… that’s a weird one cuz other assets are able to be destroyed fine but not pepecash…. It should all work or none so gotta dig into it to find out
-
im less versed on the code side of things so including how it constructs tx data in the protocol issue would be helpful.... out today but debug info might be needed on that one
-
Ma, that is weird
-
Why can’t we have nice things
- 27 July 2025 (1 messages)
-
Pepecash Still works for buying houses fast cars and yachts thought right ?
- 29 July 2025 (22 messages)
-
hrm... I was able to do a burn of PEPECASH perfectly fine from a legacy address... https://tokenscan.io/tx/206481e13b60adcd2e9ba7a4d32ee782ea65a758dd60ded8d99b9684836a30a0
-
Can't destroy pepecash · Issue #259 · jdogresorg/freewallet-desktop
I try to destroy 2100 pepecash on the latest freewallet for osx and it doesn't calculate the tx fees. If I click the YES button to confirm, the window disappears without the tx being confirmed....
-
You successfully destroyed 1 XCP a while back too, but I know that myself and others have been unable to do destroy txs. Both PEPECASH and COMNCOCOCASH.
I’m on a hardware wallet, the few folks I was trying to help were on software -
I dont doubt you and others are having issues... but need additional details about what exactly was in the API request so i can try and reproduce... could be an occasional API request to counterparty-core failing... could be related to the type of address the request is originating from.. could be related to the memo or its length.. having additional details about what EXACTLY is in the API request when it fails to work properly would be very helpful in helping reproduce any issue... Pulling up the debug console and dumping the Request URL would give the additional details i'm looking for... in Freewallet... click the Freewallet Logo, then "Debug" button.. click the "Network" tab then the "Fetch/XHR" button... that will show the XHR requests... then try making your request again and if it fails, let me know the exact URL your trying to access
-
-
Looks like this.... try a destroy.. see the "destroy?asset=PEPECASH"... click on it.. click the "Headers" tab if not already shown, then copy and paste Request url.... having these details logged on github will help track down the issue...
-
Just tried another PEPECASH destroy, from a segwit address, and a longer memo... still had no issues
-
-
Tough to track down exactly what the problem is if I am not able to reproduce it.
-
hrm... looked at your issue... https://github.com/jdogresorg/freewallet-desktop/issues/249Destroy function not working on Apple laptop with Freewallet 2.0.3 · Issue #249 · jdogresorg/freewallet-desktop
Wallet address: 1BWF35fdjbhLdRMCenguJ5HuL4CvjtXwJe Attempted to destroy 14,700 PEPECASH twice. Clicking the green "destroy" button does create the transaction or give an error message. No...
-
You took a screenshot showing the exact details I needed to reproduce the issue... seems like the issue is related to the quantity trying to be destroyed... anything under 1000 and it works fine... anything over 1000 and I see no fee estimation request... gonna guess it is something broken in freewallet... dunno why it just now started presenting itself... but does appear I can reproduce teh issue
-
will log the details and see if I can dig into it and get a fix tomorrow
-
Okay, I’ll try a destroy from my trezor and report back. If I can I’ll also do one from my old non hardware wallet
-
pretty sure I dont need you to do that... pretty sure the issue is something funky in the quantity processing and a comma being in the quantity field... will dig into it tomorrow.. think I have what I need already as far as debugging goes.. thanks for your patience as I work on a fix
-
I think you may be on to something with the quantity being over 999. I just successfully destroyed 1 COMNCOCOCASH from my Trezor
-
Although, when I try to display the transaction I am getting an HTTP Error 500. I can see the tx on blockstream and on horizon
-
-
Horizon Market | Trade Bitcoin NFTs & Counterparty Tokens
Horizon Market is the home for Bitcoin NFTs like Rare Pepes and Spells of Genesis. Trade Counterparty assets with trustless, one-confirmation swaps.
-
Hi y'all -
Hows xcer holding up? 😂
-
Not as good as buying burgers in Ibiza
FreeWallet Chat
Public archive of Telegram messages.
- 01 Jul 2025 (9)
- 02 Jul 2025 (24)
- 05 Jul 2025 (5)
- 06 Jul 2025 (1)
- 07 Jul 2025 (50)
- 08 Jul 2025 (42)
- 09 Jul 2025 (2)
- 10 Jul 2025 (5)
- 11 Jul 2025 (4)
- 12 Jul 2025 (1)
- 14 Jul 2025 (1)
- 16 Jul 2025 (13)
- 18 Jul 2025 (1)
- 23 Jul 2025 (3)
- 24 Jul 2025 (27)
- 25 Jul 2025 (2)
- 26 Jul 2025 (12)
- 27 Jul 2025 (1)
- 29 Jul 2025 (22)