Feathercoin daemon and wallet production version 0.17.0.1

problem with payments - "not transmitted, in conflict"


  • Regular Member | Tip mekhane

    I have this problem with transation made a couple of hours ago from my android wallet. It states: “This payment has not been transmitted”(translated from spanish). What can I do about this? Feathercoins are not available anymore for me, but payment has not been accomplished.

    Last summer I had a similar issue with my qt wallet as I did a transaction that says: “In conflict” (also translation from spanish), but since it had only happened once I just dismissed it and assumed the cost… but this second experience makes me fear about the possibility of loosing value randomly, and something that happens twice will sure happen a third time. Why is this happening? Can I solve this somehow?
    Thanks


  • Moderators | Tip Wellenreiter

    I’m not aware of any problems with the Android wallet, but the message implies, that there was a fork, when you tried to send your FTC. If the BC switches to the longest chain and your transaction accidentally was on the shorter chain, all transactions on the shorter chain never happened and some of them can’t even send to the block chain at all.

    Normally you should be able to send the coins after some minutes. I assume, that most fork situations are solved withing less than 15 minutes, so your problem should be short lived, but I’m not the greates expert on the BC behavior, so others may have a better explanation


  • | Tip mirrax

    @mekhane I have one conflicted payment in core 9.3


  • Regular Member | Tip mekhane

    @mirrax Yes my “conflict” problem was also on 9.3.0 back last summer. I still have those coins “not avilable” but there.


  • Regular Member | Tip mekhane

    @Wellenreiter Thanks for your explanation I have to get more information on that… time has passed and my wallet still states “this payment has not been transmitted…” I am afraid I will never see those coins again… It is not that I loose a fortune, but my confidence on BC tech goes down in some way… I would not like that to happen again, or at least I would like to know why… Best!


  • Regular Member | Tip RIPPEDDRAGON

    @mekhane Do you have the block or transaction id from when you sent it? What is your ftc address that you are using to store the funds and how much did you send? All important information if you want us to take a deeper look.

    Thanks,

    Ripped


  • Moderators | Tip wrapper

    @mekhane said:

    @mirrax Yes my “conflict” problem was also on 9.3.0 back last summer. I still have those coins “not available” but there.

    I’d recommend, back up the data files and re install from scratch.

    In case you have synced with a fork, which later dissolved, leaving your database out of sync with the real blockchain (i.e. your own mini fork.)

    Or do a fresh install and sync somewhere else, then copy in you back-up dat file.

    I’m sure there should be a similar procedure for the “Mobile Wallet”.


  • | Tip mirrax

    @wrapper said:

    @mekhane said:

    @mirrax Yes my “conflict” problem was also on 9.3.0 back last summer. I still have those coins “not available” but there.

    I’d recommend, back up the data files and re install from scratch.

    In case you have synced with a fork, which later dissolved, leaving your database out of sync with the real blockchain (i.e. your own mini fork.)

    Or do a fresh install and sync somewhere else, then copy in you back-up dat file.

    I’m sure there should be a similar procedure for the “Mobile Wallet”.

    i am synchronizing fresh 0.9.3 it is painfully slow. I will let you know the result.


  • Regular Member | Tip mekhane

    @wrapper Indeed very much right!! That you said fixed my issue, I “re-synced” the whole blockchain in my android wallet and the “unsent funds” are back in my pocket again. I will try also to do so in my qt wallet and let you know. Really nice and smooth! Thank you all for being so kind supporting my questions. I should have tried that before asking! FTC community rules!


  • Moderators | Tip Wellenreiter

    Good to hear, that your problem is solved.

    I’ve market the thread as ‘solved’. If you don’t agree, you can flat is as unsolved with the topic tools located at the first post