Offline mode implemented
This commit is contained in:
@@ -16,6 +16,7 @@ similar third-party projects.
|
||||
* Sending TRX/USDT/USDC on all supported networks
|
||||
* Freezing (for energy) and unfreezing TRX on all supported networks
|
||||
* Ability to connect to custom nodes or TronGrid API (with your own API key)
|
||||
* Offline mode for send/freeze/unfreeze transactions
|
||||
* No filesystem interaction (that's a feature, not a bug: see the FAQ section)
|
||||
* Full scriptability: send/freeze/unfreeze transactions require manual approval
|
||||
but it actually can be turned off with a special commandline parameter for the
|
||||
@@ -145,9 +146,25 @@ Again, the amount of TRX is entered as a floating point value.
|
||||
|
||||
Keep in mind that it takes up to 72 hours to unfreeze your TRX assets.
|
||||
|
||||
-- Offline operations --
|
||||
|
||||
The send trx, send usdt, send usdc, fre trx and unf trx subcommands support the
|
||||
-o flag that, after the "Success:" line, outputs a JSON of a signed transaction.
|
||||
You can copy or otherwise transfer this output to a different machine running
|
||||
kisstron and broadcast it to the network with bro trx subcommand:
|
||||
|
||||
./kisstron.py bro trx [netopts]
|
||||
|
||||
You can then paste the transaction JSON into the input field, press Enter and,
|
||||
unless -nc flag is passed too, confirm sending the transaction by entering yes.
|
||||
The transaction will be broadcast and processed as usual.
|
||||
|
||||
Keep in mind that Tron transactions expire very quickly, so you have a limited
|
||||
time window between signing and publishing them.
|
||||
|
||||
== FAQ ==
|
||||
|
||||
- Can I trust it?
|
||||
- Can I trust this wallet?
|
||||
|
||||
The author trusts it. In fact, kisstron was created because of lack of decent
|
||||
FOSS Tron wallets for Linux/BSD desktop operating systems. However, it cannot
|
||||
@@ -179,9 +196,8 @@ No. The underlying tronpy library signs all transactions offline, so the
|
||||
private key never leaves your machine. It uses libsecp256k1 via coincurve
|
||||
library binding for transaction signing.
|
||||
|
||||
Ability to implement offline mode (transactions are created and signed on one
|
||||
kisstron instance without Internet connectivity, then broadcast from another)
|
||||
in the future versions is being studied.
|
||||
You can also use offline mode to split signing and sending transactions, as
|
||||
shown in this document.
|
||||
|
||||
- Why doesn't kisstron support TRC-10, multisig, witnesses, history etc?
|
||||
|
||||
|
||||
Reference in New Issue
Block a user