Automated export of transaction ID [$200]

[gazdagruja]

Is there a way export the transaction ID from the wallet to be used in another application, specifically to a database management system?

---

There is a $200 open bounty on this issue. Add to the bounty at Bountysource.

[guruvan]

If you'd like it automated, using the daemon mode of Encompass, and the payto function, Encompass will report the txid to stdout.

[Kefkius]

"Wallet > Export History" in the menu bar. Currently by default the file is named "electrum-history". I'll change that when I put implement exporting the history for all chains to one file.

[gazdagruja]

Can the export of wallet transaction history be done automatically after every transaction?

[Kefkius]

@gazdagruja It shouldn't be too hard to make a small plugin that does that. I'll see if I can do that.

[gazdagruja]

thanks, it would be of great help.

[gazdagruja]

@Kefkius Could you make a plugin that automatically exports the wallet history as a .json file to a specified location and under a specified name? Would a donation help speed up the process of solving this issue?

[Kefkius]

@gazdagruja The next version of Encompass (release goal is July 4th) will have this functionality. A bounty, donation, etc. isn't required to get this done, but we certainly wouldn't turn one down. You can donate most easily through our Bountysource.

Thanks for using Encompass. This took a while because it depends on the new updates to our plugin system.

[gazdagruja]

@Kefkius Thank you for solving the issue I've posted! I have been trying to implement this update myself but unsuccessfully. I will keep trying but I hope that the new version that was meant to be released on July 4th will be available soon.

[gazdagruja]

Greetings @Kefkius & @guruvan, I've seen that the title of the issue has changed but without any other comments on the subject. This is new for me, so I have to ask a question:
Does my payment of the bounty you placed on Bountysource mean there will be a wallet released with this feature? I've never used Bountysource so some insight into the further progress of this feature would be very appreciated

[guruvan]

@gazdagruja - Yes! :) We'll have this feature added into the next release of Encompass. We are currently solving an issue preventing some chains' servers from dealing with chain reorgs correctly, so that new coins can be operational at release time. As soon as we solve this issue Encompass 0.6.0 will be release, with the Automated Export feature you've requested. Thank you very very much for the bounty!! Definitely helps a bunch!! :)

[gazdagruja]

Thank you for your effort, I'm glad the bounty helps. I will further reward your effort when I include this feature into my project and launch it successfully! I don't want to be pushy or hurry you, but an ETA of a stable release with this feature would really help me organize my time.
Good luck resolving the issue :)

[guruvan]

@gazdagruja I'm a little hesitant to set a date untill we have the above issues worked out - however, we should have a release within 1 week of that time, and I don't expect it will take us much longer to find this last issue. We're working hard bringing up servers for 13 coins this week, and expect to find the problem in doing so.

[gazdagruja]

Greetings @guruvan, the anticipation is palpable! :) I hope everything went according to plan and I was just hoping to get a status report on the whole caboodle.

[guruvan]

@gazdagruja Great News! We've been working to verify server code which was having trouble with reorg (and we see similar in upstream bitcoin electrum server AFAICT) - We have been testing older code, and have a stable base at this time. I expect to produce a prerelease build in the next 24-36hrs. If you'd send your email I'll send you the link for that prerelease as soon as it's available, and you can have a test (and let us know how it works before final release, and if any change is needed for your purpose)

[guruvan]

I'm available @ [email protected]

[gazdagruja]

@guruvan to quote Cazablanca: "I think this is the beginning of a beautiful friendship!" :) I will send you an email right now!

[guruvan]

:) Awesome - delighted we can work together!

[gazdagruja]

:-) It works, but I also need to be able to export it under a certain name. It keeps returning to "encompass-history.json" and to the default path also

[gazdagruja]

I have also noticed that the structure of the .json file has changed compared to the 0.5.0 export.
Is this structure final, because I will need to adjust my code to work with it.

[Kefkius]

@gazdagruja You say the filename is changing back to the default one? I can't seem to duplicate that.

Also, at this point, you seem to be the only person requesting this so it's possible that we can change the format to something that works for you.

[gazdagruja]

My bad, I forgot to change the plug-in settings. Everything is working properly!

As for the format, the "<" and ">" characters in the label string seam redundant as the value string already contains a + or - symbol at it's start. Furthermore, the first few characters of the transaction ID in square brackets are also redundant as there is a full transaction id within the .json, it would work better for me if this label field would just simply contain the address as it did previously in 0.5.0.

[Kefkius]

@gazdagruja I've added an option for exporting "minimal" labels - just the address for unlabeled transactions - to the release branch.

Those changes from 0.5.0 are for quick visual distinction between transactions (e.g. when looking through wallet history).

[guruvan]

@gazdagruja we'll run a build of this today 7 send you a link - expect a final release to come this Friday.

[IcedQuinn]

@gazdagruja we'll run a build of this today 7 send you a link - expect a final release to come this Friday.

Did this ever happen?