- 01 September 2023 (19 messages)
-
Joined. -
try again... I just did a tx no problem -
Joined. -
I have a btc transaction stuck for weeks now -
Blockstream Block Explorer
Blockstream Explorer is an open source block explorer providing detailed blockchain data across Bitcoin, Testnet, and Liquid. Supports Tor and tracking-free.
-
If anyone can tell me why and how to fix that would be great
-
That's a messy TX -
MAX send your balance to yourself with a $25 fee....yours at 3.89 sat/vb atm
-
From freewallet ?
-
Just asking in here cause you all may have delt with this.
That and im gettin goasted in the CP chat. kek
Looks like the link for my json is only partially loading the mp4.
https://xchain.io/asset/FAKEIJUANA
It was loading fine before it got the banner.
Not sayin thats what did it just sayin it can’t be updated.
The image plays fine on my IPFS but not on the interwebs.
Not sure why, so I reconnected the json to my token again but no change.
I would put the images on arweave and see if it fixes it but the images are locked (because it is part of a collection) I cannot.
If anyone has ever had this problem, any Ideas would be appreciated.
Some sort of IPFS update/refresh/publish that I may have not done yet? 🙏Fam -
Error broadcasting transaction
-
Green banner assets use a master json file that overrides the Description field. Any updates to the Description field you make will be ignored on xchain. -
Don’t think so, as the funds will still appear locked up in that txn until it gets dropped. You could try loading your priv key in electrum
-
Understood but why did it stop fully loading? Any idea?
-
Can’t explain that, sorry
-
Would it have anything to do with overriding the Description field in the master json?
As it happened after it got on the directory?
I know it’s just speculation if you don’t know.
If you don’t know why, do you know what options I have?
People are acquiring it and I don’t want it broken. -
Nah wat i mean mang
- 02 September 2023 (5 messages)
-
Talk to the project lead to see if they can change the pointer in the green banner json
-
Sounds like you are having some issues with some built up UTXO's and seeing some error messages trying to consolidate them all. Please see this FAQ: https://gist.github.com/davestaxcp/1e2cc086a13c9a2d045876852b57e5be#failure-to-send-not-enough-btc-in-walletFreewallet 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.
-
also a user mentioned importing into Electrum, reference this other FAQ to an understanding of why and what to do (though you may be able to do it with Freewallet)
-
Freewallet FAQ 2023 v0.9.23 - Write Up - Draft #5
Freewallet FAQ 2023 v0.9.23 - Write Up - Draft #5. GitHub Gist: instantly share code, notes, and snippets.
-
Thanks Mike. Appreciate the info fam.
- 03 September 2023 (1 messages)
-
Joined. - 05 September 2023 (4 messages)
-
Hi there,
Last time I sent my BTC, I doubled the tx fee, but it got stuck for three weeks.
Then I spent $15 to get it back.
This time at 6 times the transfer fee suggested by FreeWallet, I transferred the BTC, but got stuck again!
Is there a way to calculate the appropriate transfer fee? -
-
-
So the first time you sent BTC, you doubled the tx fee from the "high" setting?
When you mentioned spending $15 to get it back, it was from a Child Pays for Parent transaction?
You mentioned this time you did 6 times the transfer fee from the "high" setting? Is that correct?
There are already discussions on changing the way BTC fees are shown to the user here: https://github.com/jdogresorg/freewallet-desktop/discussions/156 - if you agree or want your voice heard, let the Developer know on the github!
Are you using the recent release of Freewallet.io , version 0.9.23 ? as seen here: https://github.com/jdogresorg/freewallet-desktop/releasesShow sat/vB and allow user to set fee rate · jdogresorg/freewallet-desktop · Discussion #156People often want to set the fee rate in sat/vB to know how quickly their transaction would confirm and how expensive it is relative to other transactions (regardless of # UTXOs used). The fee rate...
- 06 September 2023 (36 messages)
-
When you mentioned spending $15 to get it back, it was from a Child Pays for Parent transaction?>
I used this advice. -
You mentioned this time you did 6 times the transfer fee from the "high" setting? Is that correct?＞
Yes. -
Are you using the recent release of Freewallet.io , version 0.9.23 ?＞
Yes. -
Thank you for the reply, getting these things logged and perfected is why this chat exists
-
the bitcoin fees and mempool and vary wildly, and bitcoin blocks take quite a while to confirm... there is also the case of some functions on Freewallet costing more for various reasons (consolidating UTXO's etc)
-
Remember you can always test out rpw.wtf , counterwallet.io , rarepepewallet.com and Freeport by Joe Looney for other functions with Counterparty if you don't have a good experience with Freewallet
-
❤️ sorry we couldnt help more
-
None
-
Kinda noob question: How can I move/transfer multiple tokens (let's say around 10) from one address to another in 1 transaction through Freewallet? At the multisend tab, I will use the format "List Format: Address, Asset, Quantity, Memo (optional)". Hence I will include 10 lines with the same address & Quantity:1 where I will only change the Asset name? (I can totally skip the Memo parameter...)
Does it matter from which asset/token I right clicked & choose "send xxx to" and then selected "Multi send" instead of "Single send"?
Also if a specific address has 10 tokens in total and I would like to move everything, is it better to use the sweep function OR just move the 10 tokens in 1 transaction? (through the multi send tab) -
it does not matter what token you selected when you clicked "Multi Send" it will run off the data you set it for (not the token you originally clicked)
For an in depth view on how to format it all use this FAQ:
https://gist.github.com/davestaxcp/1e2cc086a13c9a2d045876852b57e5be#using-the-multi-send-functionFreewallet 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.
-
As for Sweep, if you are on the most recent version (0.9.23) you would have to downgrade to (0.9.22) to use the Sweep function as this has been temporarily disabled in the recent version.
-
And I am yet to to write the FAQ for the sweep function for 0.9.22.... sorry will get to it soon.... I also have to do a "Betting Broadcast" explanation as well as a little more explanation of the CIP25 Enhanced Asset Info specifications
-
if you are downgrading please follow these steps and back up your 12 word phrase and extra imported keys (somewhere safe) before doing so:
https://gist.github.com/davestaxcp/1e2cc086a13c9a2d045876852b57e5be#where-can-i-access-previous-versions-of-freewalletFreewallet 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.
-
if its 10 separate tokens I'd just use multisend - sweep is usually for 50+ or so to make it all easier
-
Keep in mind sweep requires a small XCP fee, so you will need that in the address as well
-
Concerning tx fees that will be needed for the 10 tokens multisend transaction: Is there a difference if I 'll send all 10 tokens to the same address OR to different address? I mean, the tx fees will be the same in both cases or it will vary? (I assume that tx fees will depend on the total number of tokens that I would like to move & the fee amount used/indicated for the tx)
-
You know I'm not really sure how all the fee's are calculated for Multi-Send and what parameters effect the fee, or if they do at all
-
Got it, thank you for all your answers! 💪🙏
-
when I use multi-send I just use the "High" setting and go from there and it works for me
-
In my understanding, for multisend, starting at 3 assets, it adds multisig that will result to an effective fee around 3 times lower.
It means that it will cost you more than sending 2 by 2. Never tested weep but it should be the cheapest way to do it. -
What you are saying is that -based on your experience - 1 multisend transaction (containing 3 assets) will cost more on tx fees VS sending 2 "simple send" transaction containing 1 asset each? (due to the multisig weight - extra bytes space is needed to construct the transaction-)
-
no no, I meant "multisend" with more than 2 lines
-
Without any advertising, if @davesta or @jdogresorg are interested, I've created a wallet with a so-so precise calculation on the fee based on freewallet code (missing CPFP in wip)
As FW base code was a great help to me, I'd be happy to share the fee calculation code. -
this would be huge to reference and post in the github discussion surrounding this topic: https://github.com/jdogresorg/freewallet-desktop/discussions/156Show sat/vB and allow user to set fee rate · jdogresorg/freewallet-desktop · Discussion #156
People often want to set the fee rate in sat/vB to know how quickly their transaction would confirm and how expensive it is relative to other transactions (regardless of # UTXOs used). The fee rate...
-
May be a good resource to compare the open source code if your wallet is on github as well, that topic goes more into the dev stuff and would probably be best for the github
-
maybe even a new topic, depending on how much detail it is tbh
-
Our code is not opensource and is fully reworked under react. We've just adapted the logical part of FW.
Btw, I've noticed that "custom fees" in FW for mint won't work regardless of what user tries to put in. (2 calls are made to CP, and second one always put "0", defaulting fees by CP) -
interesting, this is new to me. just for Minting a Token? - this sounds like something for the Issues section for sure
-
didnt know that
-
Faulty commit: https://github.com/jdogresorg/freewallet-desktop/commit/5b35b96d685c0ca49648be06ea08122ebf0245d6
Some missmatch in the refactoring and unscoped "fee" variable. (the wrong one is used at some point)clean up issuances code · jdogresorg/freewallet-desktop@5b35b96- created `confirmIssuance()` to display data encoding costs and confirm issuance - updated all issuance pages to use `confirmIssuance()`
-
I am not aware of any issues related to this commit, if you see an issue, please clarify the "issue" on github and how to reproduce the issue to verify it.... and I will look into it when I have some time... or better yet, submit a pull request which fixes the said "issue" 👍️️
-
https://github.com/jdogresorg/freewallet-desktop/issues/166
As I don't know how you would want to fix it, I don't feel opening a PR.Issuance Fee is ignored · Issue #166 · jdogresorg/freewallet-desktopFinal tx for issuance always use 0 for tx fee. Using local version of FW with master. When clicking on "Create Token" we can see this request sent to CP: When clicking on "Yes" ...
-
Thanks a bunch for bringing this issue to my attention. You are correct it is an issue which I can verify/reproduce... and a fix has been put in place, and will be in the next releaes of freewallet, today or tomorrow 👍️️
-
- 07 September 2023 (4 messages)
-
so I had to deal with the Sweep function today out of necessity... this feature saved a heart attack and was easy to use. So I finally wrote about it, this last entry also finally 'completed' the FAQ with the all points intended when originally drafted now included in detail:
https://gist.github.com/davestaxcp/1e2cc086a13c9a2d045876852b57e5be#using-the-sweep-functionFreewallet 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.
-
-
Also if you like Counterparty, Freewallet, RarePepeWallet, Counterwallet and what its all built on, be sure to grab a BLACKBOX.Counterparty_General_Fund from this dispenser, which is dispensed when you donate to the Counterparty General Fund! - Those bits go to the developers working on new features for the protocol!
https://xchain.io/tx/df9ea45715de0c7c20c7b5d7bcc2de23ffc58422f27a976ea6f69247479c41fc -
Ever wonder what features those were and might be in the future?
Check out the Developer timeline draft on the Counterparty forums:
https://forums.counterparty.io/t/counterparty-developer-timeline-for-counterparty-io/6675Counterparty Developer Timeline for Counterparty.ioSince publishing this post: Updating Information on Counterparty.io - #7 by davesta I have had a great amount of positive feedback to create a “History” Tab for Counterparty.io where we can display all the Counterparty Upgrades, historic developments and CIP’s in a nice, cool, user friendly way. I also mention a “User/Artist Historical Token” Timeline in the post mentioned above, but I will do a separate post for that one. Let focus just on developer updates here. It is my intention to gather...
- 08 September 2023 (49 messages)
-
Are there any plans for freewallet to support RBF (replace by fee) transactions in the future? Is this a protocol (counterparty) limitation -that has to be implemented first- or a freewallet feature -ie it is currently supported by the protocol but has to be added as a feature to the app-
-
Sometimes when I/we send multi-send transactions and kinda messed up with fees (tx ends up with less fees than wanted/needed), RBF would be a great way to fix this (import priv key to Electrum and RBF the transaction). I had sent a low fee counterparty transaction -once- (through freewallet), and my only option to "speedup" the transaction was through "child pays for parents"(CPFP). I did that through electrum, however the new "high fee" child transaction got confirmed BUT the parent low fee, remained unconfirmed. RBF tx support, would def solve this issue. With multi send it is difficult to calculate the exact fees needed -according to current mempool status- Overpay everytime -just to be on the safe side- is not an optimal solution
-
*should I ask this question to the "counterparty" channel instead? (or maybe ask there too, since moar users)? Not quite sure if it has to do with protocol or the app...
-
it's not possible for a child tx to be confirmed without a parent tx also being confirmed first, as the child spends the output of the parent, I expect you had multiple utxos in your address as of course transactions made with different utxos can be independently confirmed -
Hmm possible that was the issue...different utxos were used
-
100% .. a child can't be confirmed without its parent
-
I mention this briefly in the github discussion, would be great to hear your ideas posted there: https://github.com/jdogresorg/freewallet-desktop/discussions/165Education for "not enough btc in wallet" and UTXO support · jdogresorg/freewallet-desktop · Discussion #165
Can we add some informational links and maybe even some future modules to help with specific error popups? I am trying to educate and fix this issue by linking this error to the FAQ. And maybe when...
-
I think a "gather UTXO's" button and a "CPFP" by specific UTXO would be huge
-
just my two sats
-
So... what's the optimal solution to bump a low fee transaction (when RBF is disabled)? Gather all the utxos together in 1 transaction and send it to myself with a high tx fee? (...or something like that? Sorry, I am not too technical 😝)
-
You can't spend coins (utxos) that are yet to exist ..doing so would break bitcoin
yeah cpfp is valid solution and if you got multiple utxos then you got to be sure to include the unconfirmed parent utxo -
you too bob, get ur brain on the github
-
cant be all davesta nonesense!
-
You congregate all of the thoughts into 1. Legend.
-
i thought I was doing a cpfp tx the other day but it turns out I did a rbf. was not intentional .. everyone can make mistakes
-
I used cpapi to create n then used freewallet to sign n broadcast .. then used freewallet to do a subsequent tx but i did not refresh my balance first so freewallet was unaware of my new utxo .. school boy error lol
-
Heyo any idea when latest FW release will support Sweeps?
-
-
interesting, I was wondering how you might use the sign transaction feature, I've never used it before.... would love a good expansion for this page for use cases and on how to do it and why:
https://gist.github.com/davestaxcp/1e2cc086a13c9a2d045876852b57e5be#signing-a-transaction-using-freewalletFreewallet 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.
-
not sure but I would guess it will be usable again in the next release, when I did it yesterday I had to revert back a version to 0.9.22
-
i wrote how to use it here tho!
-
-
the why part is when you use the CP API to create a transaction it returns an unsigned tx hex so you then need to sign that tx hex with the appropriate private key before being able to broadcast it to the network and having it accepted into the mempool
-
you should never blindly sign unsigned tx hex without first decoding it and verifying it is what you want to sign if you did not create said tx hex
-
huh! will have to look in more to this process. It is very new to me. Would you mind writing it up as a reply to tweek the User Manual/FAQ in the github so we can include some safety precautions in the FAQ's?
https://github.com/jdogresorg/freewallet-desktop/discussions/138Freewallet FAQ 2023 v0.9.23 - Write Up - Draft #5 · jdogresorg/freewallet-desktop · Discussion #138It has been asked for and needed for some time now, so I present the - Draft 5 of the Freewallet FAQ I used Freewallet Desktop v0.9.23 to write this up with the help of the Counterparty Forums, Cou...
-
jdog has a new tool to decode txhex that perhaps could be useful when it comes to unsigned tx hex and could be mentioned here in your documents.
I believe there are or has been and I expect will be services that generate unsigned tx hex and the user is linked to freewallet to sign the 3rd party generated transaction, frewallet has built in callback capability for this
I have have not had the time to test it out JDogs new tool myself yet tho so can not comment more than that
but you see why the sign tx hex feature is useful in freewallet, it is an advanced use case for sure -
Coinb? The one that B0B put me on.
-
Still have to understand the TX order and how it's built. But it's a tool for decrypt Hex.
-
Broadcast and signing custom crafted TXs isn't for beginners. Imo
-
Huh can you link JDOGs tool? I saw the one for BTNS... But not one for XCP stuff
-
They're different right?
-
BTNS is a CP broadcast tx
-
But how does the process of "signing" the transaction come in with this circumstance?
-
all transactions must be signed to be broadcast and mined
anyone can create a transaction to say a coin will be spent to such an such address ... or a transaction to say some token is sent to some other user... but only the private key holders signature makes it broadcastable mineable -
huh
-
interesting. i dont know how all the bells and whistles go just yet! Would love for you to try to take a stab at explaining this better
-
i mean this
-
I could create a tx that says send all OGDavesta coins and tokens to me using a sweep .. but it will only happen if you were to sign it, I obviously can't sign it and you wouldn't blindly sign it I hope
but imagine i create for you a tx that registers an asset, with a fixed locked quantity and a custom description field like these minting services do, whilst using burn keys and a custom utxo dust seting.as you didn't know how to do all that but wanted such a asset .. then you would want to sign that tx
to use the feature you simply paste in unsigned tx hex and press the sign button then the broadcast button that is all there is to it
tx hex however is a deep rabbit hole in znd of itself -
Interesting. Sounds like I'll need some more documentation on this
-
And some safety warnings
-
Don't touch my ogdavesta assets btw
-
-
Imo, something like this should be directly put in the sign tx dialog:
"""
Please be careful of what you do there.
The provider of the hex can STEAL ALL YOUR FUNDS if you broadcast.
Prefer the use of our built-in features.
""" -
dont worry only you can spend your assets they are safe as long as you don't blindly sign tx hex from strangers you meet on internets
-
I agree this should be made into a GitHub discussion as well to document this thought. I always wanted a little more documentation help within Freewallet itself to like YELL AT YOU TO NOT FUCK UP
-
I built a full wallet, I'm aware of that. I just know that most users don't know what they are doing and blindly use sign tx feature.
-
imo the walket ui should decode the tx hex and display it to the user in a nice legible format... and ask are you sure .. but even then ppl been trained to just keep clicking OK OK OK
-
Best to voice all this in the GitHub so everything can be documented there
-
But I agree entirely
- 09 September 2023 (7 messages)
-
A preferable solution would be to decode the transaction into a human-readable format that explains exactly what will happen if you sign it. Yes, this is a tall order, and bad actors might still be able to obfuscate what they’re doing, but a big scary generic warning will likely just be ignored.
Signing pre-constructed transactions is also the way you get to a MetaMask level of simplicity (for good or bad). It’s definitely a better UX that opens up all sorts of capabilities presently lacking. Even the notion of having to cut and paste strings back and forth is clumsy and antiquated.
Hiro wallet and Unisat now have one click interactivity with a few Stamp services. Is it more dangerous? Yeah, probably. Is it a better user experience? 100%. There’s always that trade-off, but I’d argue that big scary warning doesn’t really help users unless “help” is defined as… just don’t do anything Defi. -
Just because warnings are "most likely to be ignored" doesn't make them obsolete for the people that actually read User Manuals, FAQs and warnings
-
There's more reasons to educate than to not
-
What I’m saying is: a warning like that doesn’t really give the user a course of action except… don’t use this functionality.
So yeah have the warning, but actually decode the transaction into a human-readable format to accompany it. User can then make a more educated decision whether or not to proceed. -
One click interaction is a bit different. Wallets have the job to secure their users funds.
If any of those wallet gives one click interaction for unknown tx, without warn/show/confirm the user what they are doing, yeah that’s a big issue and they shouldn’t be trusted.
Otherwise, one click interaction will always do something secure with clean ux. You can just check out our one click buy or one click connect.
Allowing user to sign/broadcast unknown tx and actually make them have the habits to do it is an issue.
I agree that most tools provides clean tx. If users are used to blindly sign tx with what the app is telling him, what would happen if malicious apps promise the same thing with the same ux as trusted tools? -
that's what I suggested.. decode and display to user in a nice legible format
-
which I what I think JDog is working towards with his new tx decode tool
- 11 September 2023 (57 messages)
-
i reviewed this all and understand it just a little more @sn_noop2 and @B0BSmith what do you think about this explanation + warnings for Signing Tx's with Freewallet: https://gist.github.com/davestaxcp/1e2cc086a13c9a2d045876852b57e5be#signing-a-transaction-using-freewalletFreewallet FAQ 2023 v0.9.23 - Write Up - Draft #5
Freewallet FAQ 2023 v0.9.23 - Write Up - Draft #5. GitHub Gist: instantly share code, notes, and snippets.
-
which brings me to my next point. would it be worth it to mention how to sign BTCpay tx's WITHOUT having the auto pay feature on?
-
or just better to advise always to use autopay?
-
I am referencing: https://gist.github.com/davestaxcp/1e2cc086a13c9a2d045876852b57e5be#understanding-btcpay-and-the-btctoken-on-the-dexFreewallet FAQ 2023 v0.9.23 - Write Up - Draft #5
Freewallet FAQ 2023 v0.9.23 - Write Up - Draft #5. GitHub Gist: instantly share code, notes, and snippets.
-
which are somewhat the last two things I need for information on the User Manual/FAQ
-
-
yeah you cover the point I raised about not blindly signing a tx hex and that is I think the most important warning users need to know about this feature
-
Also noticed JDOGs tool does HEX too and not just BTNS
-
Super helpful
-
yeah it should give a clearer indication as to what the hex is all about when compared to coinb.in verify or bitcoin core transaction decode
-
Can you tell me what the clearer indication would be? How would you rewrite it? I don't personally know what a "hex is all about when compared to coinbin"
-
coinbin will decode the hex and show you the same info bitcoin core will eg the inputs and the outputs but the counterparty specific data in the op return or multisig outputs will still be rc4 encoded
-
Would be cool for the json file to be provided
-
Op, amount, transfer, address
-
i think jdogs tool decodes the rc4 encoded counterparty outputs and shows you what's going on at the counterparty level not just at the bitcoin leevel
-
can i get you to test if that is true since you are more accustomed to understanding this side of things?
-
in which i can just point to Jdog's tool as the recommended one to use, as to make it easy on the user
-
but either way i put warnings all over the place this is an "advanced" thing to do at your own risk
-
I literally say this for users who understand 'hexs'
-
I can confirm it does decode the counterparty data .. I just tested it
-
it's shows it as a json string
-
when i hear the word "hex" :
-
-
it's the only tool I know of that decodes an un broadcast counterparty hex
-
changed to:
You should never blindly sign an unsigned transaction hex without first decoding it and verifying it is what you want to sign. Especially if you did not create said transaction hex yourself. Anyone can create a transaction that "says" a function will happen, but only the private key holder signature (which is YOU as the user signing a transaction) makes this function broadcast-able and mineable to the network. It is helpful to first read a transaction and its contents in full by using a hex decoder [like this one made by Jdog](https://jdogresorg.github.io/BTNS-Decoder/) but the responsibility of signing a transaction manually is soley at the user's discretion. Please note it is recommended here to only use this hex decoder mentioned above for use with Freewallet as it is community trusted and decodes Bitcoin and Counterparty hex information into a readable JSON format. -
-
cool. any comment on this @B0BSmith ? about teaching people to use the old BTCpay manually? or just stick with the "Autopay" directions
-
I have never used BTCPay so nope no comment from me on that feature
-
well ive used it and ill say id NEVER do it manually
-
and i would rather not influence people to try to use it manually
-
as I also found a bug in the protocol itself while doing so.....
-
Lower Requirement to Trigger BTCpay Order Match from 0.001 BTC to Something Lower · CounterpartyXCP/cips · Discussion #96
Below is a test process I used, along with help from @Blockjack8 and @al_fernandz to try to use the BTCpay function using Freewallet v0.9.23 and we found orders were not matching with BTC orders un...
-
-
-
yeah best to advise people to use the AUTO mode as my understanding is it is time sensitive
-
that means this doc is just about ready to be repo'd and pull requested with the intention to be added to the documentation side of things on the Counterparty Documentation repo
-
for more critique by devs and discussion
-
but that has been my goal this entire time
-
-
it will be interesting to see others feedback too .. hopefully it helps both new and existing users
-
its god damn needed ill tell you that much
-
also will need a re-structuring and updated version of this document when adding the repo for Freewallet:
https://github.com/CounterpartyXCP/Documentation/blob/master/Developers/contributing.mdDocumentation/Developers/contributing.md at master · CounterpartyXCP/DocumentationOfficial Documentation of the Counterparty Project - CounterpartyXCP/Documentation
-
Also I am preparing to include a commit to the Documentation side of the Counterparty github that would include:
1. Adding a "Freewallet_Tutorials" Folder in the github that includes the major sections of the Freewallet User Manual and FAQ in markdown format:
- What is Freewallet?
- Freewallet Functions
- Exploring your Balances, History and the Exchange and Dispensers Tabs
- Trading Basics for BTCpay and DEx
- Common Questions and Errors Using Freewallet (FAQ)
- Getting Support
- Errors Reported on Specific Versions
2. Doing a pull request to specifically update and change the "contributing dot md" file on the Documentation to include Freewallet and "How to Submit a Bug Report" related to the updates above.
My question to you is, should I go ahead to add this documentation already written to the Counterparty Documentation (Docs) for Freewallet 0.9.23? Or wait for the next version to release and then add it at that time?
Just want to make sure I am maximizing my time correctly if this update is sooner rather than later (would be easier to just update the documentation to the newest version, then add to the Documentation for review) -
i sent this to Jdog, so theres also the possibility of getting a new update before it all gets submitted to the Counterparty Documentation repo
-
not sure yet will have to wait on response there
-
but the ultimate goal is within my sights
-
-
then i can start posting links to the FAQ linking directly to the Counterparty github and website and not just my measily old n00b gists
-
after they are all verified and critiqued and approved of course
-
-
yeah be nice for new users to have such detailed faq infos and it hopefully leads to more people enjoying counterparty
-
-
after that is the timeline data
-
and rewriting the Counterparty FAQ's a little
-
to spruce them up
-
ive done a few pulls on those already
-
but they are simpler
- 13 September 2023 (4 messages)
-
good to know this was your experience, thanks for the sharing the issue and your solution you found for it.... havent heard this issue yet as well
- 14 September 2023 (16 messages)
-
Joined. -
Joined. -
Create a support ticket on coindaddy.io n I’ll look into it👍🏻
-
No. Consolidate BTC, if won't broadcast.
-
Send your Bitcoin back to yourself
-
take a look at this FAQ and let me know if this helps you:
https://gist.github.com/davestaxcp/1e2cc086a13c9a2d045876852b57e5be#failure-to-send-not-enough-btc-in-walletFreewallet 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.
-
Joined. -
Joined. -
Joined. -
Joined. -
👀👀
-
Joined. - 15 September 2023 (76 messages)
-
If you have done many transactions on this address it's possible your total BTC amount is 'fragmented' with UTXO's.
As mentioned in the FAQ "If none of those fixes work, it is more likely this means the amount of BTC on your address is ‘fragmented’ and the total balance you see is actually been split up into many smaller parts which are called UTXO’s (Unspent Transaction Output’s)."
In this case it might be time to 'consolidate your UTXO's' and 'de-fragment' the btc data on your address.
As it is mentioned in the FAQ, this is done by sending all of the BTC on your address to yourself (back to the same address).
Sometimes many users just 'refill' their btc amount (or send more btc to the address from another place) so these functions can happen without having to consolidate your UTXO's... but know if you do this, eventually you will have to consolidate your UTXO's to clean up the btc data on the address.
This process is more of a "bitcoin" thing and less of a Freewallet specific thing as it happens to many people who have an address that they use frequently for various purposes. -
What version of Freewallet are you using?
-
-
In this case if you are still getting the "not enough BTC in wallet" message I would recommend following the instructions on consolidating your UTXOs using Electrum from this FAQ
-
i can put my freewallet private key on electrum?
-
Just make sure it's the correct wallet.
-
Correct download **
-
this is correct wallet, right?
-
That is correct
-
it's looks like i have some unconfirmed transaction , but everything is already valid transaction on freewallet
-
Freewallet does have a slow time updating from the blockchain data, but both Electrum BTC data and Freewallet BTC data can always be verified on a BTC block explorer such as blockstream.info
-
most likely, could be Freewallet 'knows' you have BTC in unconfirmed tx's but the User Interface is showing it as still in your wallet
-
wouldnt be a bad thing to add to the FAQ as general info....
-
-
Haven't done a multi-send in awhile and need to do 2 big ones tonight (about 20 assets each). Last time I tried had some trouble (the 2nd transaction fail thing)... any advice or should I just stick to single sends to avoid headache...
-
20 sends isn't that much... prolly just quadruple the suggested fee and that'll be more than enough 😛
-
better to overpay than underpay
-
will do, thanks.
-
Just curious, does changing a token description automatically charge you like x9 the miner fee? Had to do it twice last night, fee was set to low ($1.03 in BTC) and for some reason it used $18 worth of BTC for both transactions. But doing anything else used the actual proposed mining fee -
Not sure why that is happening.... it definitely should NOT.... but it is strange it has happened to you and not other users using Freewallet v0.9.23.
Since this is the second time you referenced this happened, it is probably a good candidate for a new Issue in the issues section of the github.
If you are okay with posting your address and transaction info, it would be good to include this in the Issue when drafting it as well as a screenshot or video of what Freewallet is showing you vs. what the TX info shows.
https://github.com/jdogresorg/freewallet-desktop/issuesIssues · jdogresorg/freewallet-desktopDesktop wallet for Win/Mac/Linux which supports Bitcoin and Counterparty - Issues · jdogresorg/freewallet-desktop
-
Ya that's fine ill add it to the list 👍🏻 Dont have a github account tho
-
thank you! helps alot for troubleshooting and documentation to include it in the Github, as many users that use Freewallet arent in this chat.... also helps new users if they have the same issue to see someone else is having this problem
-
cant send btc from one addy to another, trying to empty a dispenser addy keeps giving me error all diff fees and amounts same error -
-
Pic for reference
-
hey Sam M, this error is common and is written about in the Freewallet User Manual/FAQ here. Let me know if this documentation helps:
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.
-
very strange, seems like an issue worth documenting... this shouldnt happen from my understanding and if it is, it is hands down an issue that needs some looking into (especially from users on the Github)
-
thank you fren very much appreciated first time i came across, usually up the fees and it goes through
-
the FAQ for ""Failure to send not enough BTC in wallet"" is also a good one to read and the fixes there might help you too
-
im wondering here if the length of description is effecting this maybe? I can't think of a reason why it would be so enormously high though...
-
Ayyyyy. So a fren of mine this response wen trying to cahnge discription on token.
-
i just got this
-
Done all the quit reopen
-
now i have never seen this yet!
-
first time ive even seen that error
-
Great!
-
Ok so lets explore
-
wat could be the issue
-
Might be a jdog issue to help with
-
def not a common error
-
Should he do a debug console
-
tx info
-
first off I'd try changing the fee amount a little bit, see if that helps
-
looks like its for updating a description....
-
Joined. -
That isa correct ser
-
Marek is on v0.9.23?
-
Yes is on that
-
-
huh
-
-
That is wat he is getting
-
im assuming its saying "cant convert a negative integer to an unsigned tx"
just random, but MAY be related... how many tokens exist for this token he is changing the description for? -
maybe its a 0 issuance token and Freewallet is reading it as a "negative integer"?
-
It’s locked at 21
-
-
well shit
-
Right. Shall we include jdog in this one
-
I think it is a problem beyond us
-
100% - might be good to start an issue on it as well... I can't find any documentation on this
-
-
@jdogresorg Need you fam.
-
-
welcome fam
-
chillin! trying to raise some money to make it out to pepefest.lol by selling some RARE cards from XCP and Rare Pepe... and having fun helping people in here with issues
-
As porkchop mentioned it looks like you ran into something we have never seen before and will need some help from Jdog on it
- 16 September 2023 (14 messages)
-
-
lets go!!! that huge!! Marek fake rare on the way??
-
thats good to hear. weird solution if i say so myself, but happy you got it sorted out
-
Joined. -
Lots of issues with FW transactions getting stuck in the mempool. Very difficult to use in elevated fee environment. Just an observation. Seems like an important thing to improve. Hope everyone is having a great day
-
Hello, good day.
Sorry want to make sure about how to increase the fee. 🙏
Cc @ctramount -
Is it simple as send the btc to the same addy?
-
Joined. -
Exactly CPFP.
-
use this FAQ for Child Pays for Parent:
https://gist.github.com/davestaxcp/1e2cc086a13c9a2d045876852b57e5be#help-i-used-too-small-of-a-fee-and-my-transaction-is-not-confirmingFreewallet 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.
-
Finaly, it works thank you very much sir @NorthrnSatosh @davesta cc: @ctramount 🫡
- 17 September 2023 (1 messages)
-
Joined. - 18 September 2023 (1 messages)
-
Joined. - 19 September 2023 (15 messages)
-
Welcome everyone! Check pinned for the most detailed documentation for Freewallet.io
-
New version out fam:
https://github.com/jdogresorg/freewallet-desktop/releases/tag/v0.9.24Release v0.9.24 · jdogresorg/freewallet-desktopAdded support for pooling ADS donations Added support for reviewing license agreement Started passing forward advanced params in CP API requests Fixed issues with sweep form Fixed issue with fee no...
-
FreeWallet (@FreeWallet) on X
Happy to announce the release of version 0.9.24 of FreeWallet Desktop wallet for Windows, Macintosh, and Linux. This update includes better address management tools, auto-lock, bugfixes, improvements, and more! #Bitcoin #Counterparty $XCP #Freewallet https://t.co/s4jRuSiTfk
-
you might want to take a look at it... the address management has been retooled slightly ("Options" removed from "Change Address" screen... and the "Options" pushed up to "Address Options" in the main screen) .... Prolly need to tweak/update some docs after this release 🙂
-
LOVE this JDOG
- great information
- Bounty for betting is shown!!
- License agreement added on About page
- issue I see is the "decentralized betting system" links to the old docs page which doesn't show the info: https://counterparty.io/docs/protocol_specification/#bet
- feels way cleaner when clicking around!! -
100% - need to test a few things too
-
good catch on that issue... pls create a github issue for it and i'll get the link fixed in the next release 🙂
-
already ahead of ya
-
:)
-
small link issue on 0.9.24 · jdogresorg/freewallet-desktop · Discussion #169
small issue I see here is the "decentralized betting system" links to the old docs page which doesn't show the info: https://counterparty.io/docs/protocol_specification/#bet could be ...
-
Also... the raw transaction signing now tries to decode the tx data and extract any counterparty data and display it to the user BEFORE signing now
-
-
-
- 20 September 2023 (101 messages)
-
amazing integration - THANK YOU
-
Your doing pretty amazing work yourself here with all your support and documentation updates 🙂 Much appreciated sir 🙂
-
Great work all around. Thank you ser 🐸🐸
-
can you explain this:
-
in detail for a pleb like me?
-
Is it in relation to this issue? https://github.com/jdogresorg/freewallet-desktop/issues/166Issuance Fee is ignored · Issue #166 · jdogresorg/freewallet-desktop
Final tx for issuance always use 0 for tx fee. Using local version of FW with master. When clicking on "Create Token" we can see this request sent to CP: When clicking on "Yes" ...
-
sorry posted in the XCP chat thinking I was in support chat
-
freewallet-desktop/js/freewallet-desktop.js at 04ae16043f0d2c371089b438d0b737dde121f947 · jdogresorg/freewallet-desktop
Desktop wallet for Win/Mac/Linux which supports Bitcoin and Counterparty - jdogresorg/freewallet-desktop
-
this is the specific commit https://github.com/jdogresorg/freewallet-desktop/commit/15db3268ac94bb1a042e62457e69772e57970914code cleanup · jdogresorg/freewallet-desktop@15db326
- Added `setAdvancedCreateParams()` to handle setting advanced CP API request params - Started passing forward dust preferences in every API request (issue #132) - Forced `allow_unconfirmed_outputs...
-
just cleaned up the code a bit 🙂
-
wrote up a little feedback on my user experience testing sending BTC to myself (consolidating UTXO's):
https://github.com/jdogresorg/freewallet-desktop/discussions/156#discussioncomment-7052387Show sat/vB and allow user to set fee rate · jdogresorg/freewallet-desktop · Discussion #156People often want to set the fee rate in sat/vB to know how quickly their transaction would confirm and how expensive it is relative to other transactions (regardless of # UTXOs used). The fee rate...
-
hi, i have updated my freewallet to version 0.9.24, but now i've lost my 1st address. i have log out and log in back but still the address is missing
-
try adding the addresses back in this way:
-
-
-
that will be your Legacy addresses
-
-
and these would be your Segwit addresses
-
you added the addresses and they still dont show when you go to "Change Address"?
-
keep in mind this version came out today and I am still new to the UI myself
-
this used to be my 2nd address, but now become my 1st
-
interesting thats weird - remember you can always use the older versions if this one is having issues
-
you could also get your specific private key for that specific address from 0.9.23 and import it into 0.9.24 as a work around
-
side note:
-
-
i just noticed this jdog!
-
wow.
-
Taproot = Ordinals
-
-
just as a statement here i dont know how ready this is or if it is just a placeholder for a future release
-
nor do I have the right amount of understanding yet to write the correct information it
-
just cool to see
-
cips/cip-0030.md at master · CounterpartyXCP/cips
Counterparty Improvement Proposals. Contribute to CounterpartyXCP/cips development by creating an account on GitHub.
-
CIP: 30
Title: Taproot Support -
discussed here:
-
CIP 30: Taproot Address Format · CounterpartyXCP/cips · Discussion #101
Discuss CIP30: Taproot Support here. Please stay on topic and be respectful. Is there anything in the proposal that is unclear or needs clarification? Objections or concerns should be documented he...
-
-
-
Same as like me sir...
and i can't unlock the wallet -
Joined.
-
Joined. -
-
i cant send the funds because its locked, eventho i already unlocked it
-
-
import your private key into electrum if you need to send funds while they found a solution for freewallet -
the truth is, what i actually try to send is the assets, can this be done in electrum?
-
oh sorry i don't think so... which asset? there are rarepepewallet and fakerarewallet which can help doing that if i dont mistaken
-
danks 😁 but thx for the responds
-
did you try using an old version of freewallet?
-
nope, i just update the fw today, but let me try it
-
Joined. -
Gm, my freewallet 0.9.23 desktop on mac froze two times when trying the sweep function. Had to restart it twice and no sweep possibility so far.
Known issue? -
Updated to 0.9.24 and does not freeze anymore🙏🏼
-
sweep is disabled on 0.9.23 - but was brought back for usability with 0.9.24
what you are seeing is referenced here:
https://gist.github.com/davestaxcp/1e2cc086a13c9a2d045876852b57e5be#using-the-sweep-functionFreewallet 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.
-
is this v0.9.24?
-
try downgrading back to 0.9.23 if this issue is happening with the new version
-
this is strange to me as you are searching the address in the bottom left hand side... when Freewallet loads up it automatically shows you #10 legacy addresses and #10 segwit addresses... and you mentioned it was Address #1 before that was missing when you updated from 0.9.23 to 0.9.24.... then downgraded back to 0.9.23 and cannot see it?
-
Since Freewallet is a deterministic wallet it generates the same addresses from your 12 word phrase.... I have never heard of the 'Address #1' being lost or not shown.... you can always try using counterwallet.io , rpw.wtf or rarepepewallet.com with the seed phrase to see which addresses you can access to compare what Freewallet is showing you
-
Freewallet FAQ 2023 v0.9.23 - Write Up - Draft #5
Freewallet FAQ 2023 v0.9.23 - Write Up - Draft #5. GitHub Gist: instantly share code, notes, and snippets.
-
It's most likely viewing Address index #1. But indexes start at '0' afaik.
-
Just a possibility why their first address not showing?
-
yes the newest
-
okayy
-
Having the same issue here, I downgraded and now I’m having it on every version I download -
Save PrivKey and Seed Phrase before Update.
-
I've tried to send an asset today via latest version and got "error could not sign" Tried a few things , restart computer, log out and in again but error remained. Downgraded to 0.9.23 and same error occured. Closed freewallet reopened and after like 6-7 tries finally tx was good on 0.9.23. Saying this as it could be that there's some network instability rather than Freewallet version issues. 🤷♂️
-
Cache no?
-
Full Uninstal then full fresh install
-
I haven't upgraded yet. No issues on the old one for me
-
Or the web browser
-
Jdog quiet. He probably making tweaks.
-
Possibly, No pro at full uninstalling on mac, usually just replace old version by new version.
-
If more errors for sure I‘ll try that, at the moment I am good. Thanks for the hint. 🙏🏼
-
Cp has taproot integration ready to go… but, gotta put out a maintenance release that addresses some issues first before we can support taproot…. So yes, this is a placeholder for coming integration…. All code is written, just needs to get integrated into CP and then into freewallet… prolly around Christmas
-
I added an auto-lock feature that you can edit in settings tab…. By default auto-locks wallet after 15 mins
-
digging into this... seeing same behavior here...
-
issue fixed... creating new builds now... gimme a few n i'll post link here when new builds are done (i'll just replace the 0.9.24 builds and update the checksums.txt)
-
fixed issue with missing first address · jdogresorg/freewallet-desktop@2bbdac2
Desktop wallet for Win/Mac/Linux which supports Bitcoin and Counterparty - fixed issue with missing first address · jdogresorg/freewallet-desktop@2bbdac2
-
-
-
Release v0.9.24 · jdogresorg/freewallet-desktop
Added support for pooling ADS donations Added support for reviewing license agreement Started passing forward advanced params in CP API requests Fixed issues with sweep form Fixed issue with fee no...
-
New binaries posted.... if you had an issue with a disappearing first address, please download this latest release, install it, and then "logout" of freewallet and then login again with your 12-word passphrase... this will re-add the first 10 addresses back to your wallet 🙂
-
i set to 15 minutes, but it still automatically locked just after i unlocked it 😅
-
Hrm…. Can you try setting the auto lock to disabled n restart freewallet n let me know if you still have issue with it auto-locking
-
Joined. -
Hi, Has anyone had any issues with changing asset description but it still shows old image? Ive change the description but still showing the og image, but in the description is the new image link?
-
Green banner? It supersedes your description.
-
Not got a banner or anything
-
Link?
-
Pretty sure this is the wrong structure for imgur.
imgur.com/yUoIxBFLinkDiscover the magic of the internet at Imgur, a community powered entertainment destination. Lift your spirits with funny jokes, trending memes, entertaining gifs, inspiring stories, viral videos, and so much more from users.
-
I’ll check some previous ones ive done, I usually use easyasset but i know some people had issues so going back old school
-
@mikeinspace this is a previous one maybe i need to add .png
-
Ok i updated the .png .. It now shows but also shows the older gif underneath
-
-
Still showing the old easy asset info
-
I tried disabling the auto lock but the issue still persists… the auto-lock automatically jumps back to 15 minutes
- 21 September 2023 (27 messages)
-
Same issue here. I like that it forced me to create a password. I also don't like that it forced me to create a password. -
Hrm… what os you guys on? I’m not seeing that behavior here.
-
If you could create issue to recreate problem, I’ll dig into it n get it fixed…. It shouldn’t force a password
-
So I did the update, appreciate that.
It says to unlock so I make a password.
Use the password and it says -
-
I go to send something and it says.
-
-
Mac
-
Mac
-
Can you please create an issue here with the exact steps you take after logging out of the wallet…. I want to be able to reproduce here https://github.com/jdogresorg/freewallet-desktop/issuesIssues · jdogresorg/freewallet-desktop
Desktop wallet for Win/Mac/Linux which supports Bitcoin and Counterparty - Issues · jdogresorg/freewallet-desktop
-
I installed the new version, went to send, asked me to create a p/w. Did that, unlocked. Never unlocks. Also on Mac. Reinstalled previous version, still locked. hOW doEs it KNOw?!?
-
Maybe there is a file from the Application support folder I can delete? I really don’t wanna recreate the data on the wallet.
-
Issue created.
-
Joined. -
I don’t know how it knows but I did the same thing and it knows.
-
mac and windows 10
-
I believe that once it's encrypted, it's encrypted, no matter which version.
-
Yeah I ended up deleting the whole thing, files and all and downloading version 0.9.23.
All good and back to normal. Thanks for doing the github report. Appreciate you fam. Also for the vault snag. 🙏 -
😉
-
Now if I could only open the vault!
-
OOHHH NNOOO dm’d ya
-
GN guys, can i ask you something? 😅😁
-
what should i do if i get the mssg like this "Error composing send transaction via API: Insufficient BTC at address - - - To spend unconfirmed coins, use the flag --unconfirmed. (Unconfirmed coins cannot be spent from multi‐sig addresses.)"
-
because i see from the history every transaction on the address is already valid
-
this is a common error and can mean a few things:
https://gist.github.com/davestaxcp/1e2cc086a13c9a2d045876852b57e5be#failure-to-send-not-enough-btc-in-walletFreewallet 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.
-
feel free to explore that User Manual / FAQ for more information - it is also in the Pinned message if you need to reference back here to access it
-
thank youuu
- 22 September 2023 (115 messages)
-
Joined. -
good morning! I see this has been asked before, but was just wondering if anyone has found a workaround the persisting lock of the wallet after entering the password? It would be undesriable to have to delete the app and lose all wallets inside having to reinstate them all. Thanks so much!
-
unfortunately at the moment users either need to access the wallet on a new device (separate computer and use v0.9.23 or earlier) or delete and uninstall the application entirely then use the earlier version. If it is no rush, it looks like it is known by Jdog and a fix should be out soon: https://github.com/jdogresorg/freewallet-desktop/issues/171Password does not unlock · Issue #171 · jdogresorg/freewallet-desktop
Installed new version Attempt to send Asks me to create password Enter same p/w twice Unlock wallet Enter password Says is unlocked Attempt to send Says unlock wallet Unlock wallet, enter p/w Lock ...
-
I appreciate your fast answer. Will proceed with deleting the app and reinstalling since time is of the essence
-
remember to safely back up your 12 word phrase and any imported addresses private keys - if you cant do that it's best to wait at the moment
-
-
Joined. -
Gm I was just trying to multisend from 145uc1qBVTBvvQGuXCCw8z77bLJzTzDbPY and encountered error and lost 10$. Same happened while ago, what’s the problem with the multisends?
-
Yup this makes sense.
-
Utxo management tab? 👀
-
Would be cool tool utxo smart
-
many users agree this is an issue:
https://github.com/jdogresorg/freewallet-desktop/discussions/156Show sat/vB and allow user to set fee rate · jdogresorg/freewallet-desktop · Discussion #156People often want to set the fee rate in sat/vB to know how quickly their transaction would confirm and how expensive it is relative to other transactions (regardless of # UTXOs used). The fee rate...
-
^^^^ check github posted above
-
yes this is a known issue:
https://github.com/jdogresorg/freewallet-desktop/issues/171Password does not unlock · Issue #171 · jdogresorg/freewallet-desktopInstalled new version Attempt to send Asks me to create password Enter same p/w twice Unlock wallet Enter password Says is unlocked Attempt to send Says unlock wallet Unlock wallet, enter p/w Lock ...
-
what version are you using?
-
Yes, but utxo management has to be more then consolidation of UTXOs
-
For the Ordinals concepts
-
CounterParty and Stampchain we don't have to worry about such things. But ordinal theory requires management to avoid spending of sats
-
Don't really matter to me....but have seen Ordinalswallet provided an in wallet tool for UTXOs
-
Xcp and Stamps, is my favor
-
please post your response in the github
-
in my opinion (other than fixing the locking issue) - UTXO correct fee estimation in sat/vb and UTXO management is the most important thing that needs to be addressed
-
would love to have your viewpoint published there
-
especially if we see taproot being supported soon!
-
Haven't created an account on their. But I re read your documents
-
As I said. You've done a great job consolidating our thoughts and suggestions into
-
please do, the github needs your brain
-
im not going to always 'consolidate peoples opinions'
-
too much work for one davesta
-
Nooooooo
-
Lol
-
🙏🙏🙏
-
1 is enough 🐸🐸
-
i will, though, vehemently suggest more community support for showing the sat/vb slider I mentioned here
-
if you dont post in the github = it probably wont be taken seriously
-
-
Understand that.
-
Not everyone uses TG. I get it.
-
would love a day where im not the main mofo posting in the discussions
-
-
*hint hint*
-
🙏🙏
-
Joined. -
Hi all! Thanks for the amazing work with Freewallet.
-
Has anybody encountered an "error signing transaction" with the recent upgrade?
-
check these two FAQ's as it could be a couple things:
-
Freewallet FAQ 2023 v0.9.23 - Write Up - Draft #5
Freewallet FAQ 2023 v0.9.23 - Write Up - Draft #5. GitHub Gist: instantly share code, notes, and snippets.
-
Freewallet FAQ 2023 v0.9.23 - Write Up - Draft #5
Freewallet FAQ 2023 v0.9.23 - Write Up - Draft #5. GitHub Gist: instantly share code, notes, and snippets.
-
The error message isn't shown in the FAQ (maybe we can add it). I un- and re-installed, logged out and restored my Freewallet with the seed phrase, and played around with the fee. Still getting the same problem, even with different assets. With debug enabled, this is the last thing in the console:
error = TypeError: this.priv.toAddress is not a function
at CWPrivateKey.getAddress (util.bitcore.js:105:20)
at util.bitcore.js:281:24
at Array.forEach (<anonymous>)
at CWBitcore.genKeyMap (util.bitcore.js:280:17)
at CWBitcore.signRawTransaction (util.bitcore.js:308:28)
at signTransaction (freewallet-desktop.js:3354:23)
at freewallet-desktop.js:2422:13
at freewallet-desktop.js:2962:13
at Object.success (freewallet-desktop.js:2935:17)
at c (jquery.min.js:2:25304) -
this is with 0.9.24?
-
have you tried downgrading to the previous version 0.9.23?
-
Yes.
-
Actually, no :) I'll do that.
-
Well would you look at that. It worked. I'll just stay on 0.9.23 in that case. The release notes didn't seem to indicate a burning need to upgrade to 0.9.24 for security reasons.
-
the security jump from 0.9.22 to 0.9.23 is important but the main use cases for 0.9.24 is the sweep function, the support for decoding XCP transactions in sign transactions and a few other quirks with issuance fee's
-
check all upgrades and fixes here:
FreeWallet Chat
Public archive of Telegram messages.
- 01 Sep 2023 (19)
- 02 Sep 2023 (5)
- 03 Sep 2023 (1)
- 05 Sep 2023 (4)
- 06 Sep 2023 (36)
- 07 Sep 2023 (4)
- 08 Sep 2023 (49)
- 09 Sep 2023 (7)
- 11 Sep 2023 (57)
- 13 Sep 2023 (4)
- 14 Sep 2023 (16)
- 15 Sep 2023 (76)
- 16 Sep 2023 (14)
- 17 Sep 2023 (1)
- 18 Sep 2023 (1)
- 19 Sep 2023 (15)
- 20 Sep 2023 (101)
- 21 Sep 2023 (27)
- 22 Sep 2023 (115)
- 23 Sep 2023 (12)
- 24 Sep 2023 (17)
- 25 Sep 2023 (8)
- 26 Sep 2023 (10)
- 27 Sep 2023 (15)
- 28 Sep 2023 (1)
- 29 Sep 2023 (14)
- 30 Sep 2023 (22)