Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bulwark-cli support transaction export #119

Open
jdonohoo opened this issue Oct 30, 2018 · 6 comments
Open

bulwark-cli support transaction export #119

jdonohoo opened this issue Oct 30, 2018 · 6 comments

Comments

@jdonohoo
Copy link

Title says it all, programmatic access to exporting transactions via cli would be awesome.

@ghost
Copy link

ghost commented Nov 6, 2018

We do have gettransaction and gettxout from the cli plus a few other get commands, let us know if this suffices

https://github.com/bulwark-crypto/Bulwark/blob/master/doc/bulwark-core/Bulwark-API-Calls.md#full-list

@jdonohoo
Copy link
Author

jdonohoo commented Nov 8, 2018

@padraiq I was referring to programmatic access to the Export button on the transaction tab.

@dustinengle
Copy link
Contributor

RPC Commands to pull transaction information for accounts.

listaccounts

This will list the accounts and their balances.

listtransactions ( "account" count from includeWatchonly)

Returns up to 'count' most recent transactions skipping the first 'from' transactions for account 'account'.

Arguments:
1. "account"    (string, optional) The account name. If not included, it will list all transactions for all accounts.
                                     If "" is set, it will list transactions for the default account.
2. count          (numeric, optional, default=10) The number of transactions to return
3. from           (numeric, optional, default=0) The number of transactions to skip
4. includeWatchonly (bool, optional, default=false) Include transactions to watchonly addresses (see 'importaddress')

This will return the transactions for an account.

@jdonohoo
Copy link
Author

jdonohoo commented Jan 4, 2019

I wouldn't call this the same, as the outputs are the raw non pretty cleaned up stuff that the export button provides... It's a work around that requires some heavy data massaging / further commands to get the same dataset. @dustinengle

@dustinengle
Copy link
Contributor

Would a RPC command like exporttransactions {path} that would export the .csv file to the path provided work? The {path} value would be something like /home/user/Documents/bwktxs.csv for example so the whole command would be bulwark-cli exporttransactions /home/user/Documents/bwktxs.csv to run it from the command line.

@dustinengle dustinengle reopened this Jan 4, 2019
@dustinengle dustinengle self-assigned this Jan 4, 2019
@dustinengle dustinengle added this to the 2.2.0.0 milestone Jan 4, 2019
@jdonohoo
Copy link
Author

jdonohoo commented Jan 4, 2019

@dustinengle yea, that's literally how I was thinking when I requested this originally.
Sorry, that I wasn't more clear. I was thinking a command like bulwark-cli exporttransactions and it defaults to your bulwark directory, and the path is an optional arg.

Something Like This:
Windows Default: %appdata%/bulwark/bwk-transactions.csv
Linux Default: ~/.bulwark/bwk-transactions.csv

@ghost ghost closed this as completed Jan 6, 2019
@ghost ghost reopened this Jan 6, 2019
@dustinengle dustinengle removed their assignment Feb 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants