Q&A about the newly introduced "Scheduled Transactions" feature to prevent front running the unconfirmed transactions pool.
See also
https://nxtforum.org/general-discussion/the-story-of-the-ignis-crowd-sale-(first-round) which explains the motivation for this feature.
Q: what's the priority to execute these buy orders, when they will hit blockchain? Same as usual?
A: As soon as the node scheduler storing the scheduled transactions sees the exchange offer as an unconfirmed transaction, it will immediately broadcast your currency buy transactions.
And they will compete with the rest of the transaction for inclusion in the next block, according to the usual transaction priority.
Q: So, if I understand correctly, this new stuff is for users to make buy transaction in advance, instead of lurking near PC and try to be fast?
A: Exactly
Q: And if my advanced buy order is not filled, I need to repeat the same before the next batch? Am I right, this new stuff do not solve MAAC problem?
A: It does solve it, since MAAC found a way to submit his transaction while the Jelurida exchange offer was still unconfirmed and invisible to the UI.
With 1.11.7, every scheduled transaction will do exactly that.
Q: When Jelurida exchange offer becomes valid? Only when approved or broadcasted?
A: When the Jelurida exchange offer is still unconfirmed the scheduler will submit the buy orders
Q: will not wait for approval of it?
A: They will all approve in the same block, the exchange offer will have the earliest arrival time so the currency buy transactions will match it in the same block just like MAAC did it manually
Q: But looking at history, approval account approves exchange offer few block later. I feel some confusion here. Always thought, that without approval any transaction is not "valid".
A: The exchange offer will no longer be phased, just regular transaction
Q: And if my scheduled buy order is not filled, I need to repeat the same order before the next batch?
A: Yes, as usual, however you'll compete on level terms with everyone else
Q: What do I need in order to submit a scheduled transaction?
A: You'll need a full node running on localhost, or a remote full node to which you have the admin password. As usual your passphrase is never submitted to the remote node
Q: Where can I see my scheduled transactions?
A: Use the getScheduledTransactions API
Q: What if restarted my node?
A: You'll need to resubmit the scheduled transactions
Q: What is the maximum number of transactions I can schedule?
A: 100 per node
Q: How do I delete scheduled transactions?
A: From the "Scheduled Transactions" page in the wallet.
Q: Can I use the jelurida.com public node to post scheduled transactions?
A: No, since we do not reveal the admin password for our public node
Q: Do I see my scheduled transaction as unconfirmed or somewhere in the wallet?
A: You see it in the "Scheduled Transactions" page in the wallet.
Q: Can I schedule a phased currency buy transaction?
A: No
Q: If I am running a full Nxt node on a vps which I have control in but don't fully trust, so I don't want to expose my passphrase to it. How should I submit a scheduled transaction on the vps safely?
A: When you submit scheduled transactions to a remote node, your passphrase is not submitted to the remote node. You do need specify the admin password of the remote node in the account settings of your wallet.
Q: How do I know that my scheduled transactions were indeed submitted?
A: If your transactions were submitted you will see them in your wallet dashboard and you can follow your balance changes in the account ledger page as usual.
