Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

DAWN-376 ⁃ migrate account_history_plugin to eos-noon branch #1046

Closed
blockone-syncclient opened this issue Jan 8, 2018 · 3 comments
Closed
Assignees
Milestone

Comments

@blockone-syncclient
Copy link

blockone-syncclient commented Jan 8, 2018

(This ATC needs to be fixed once DAWN-466 has been merged)

ATC:
Can be run on local or public testnet (if public testnet, then node2 will need to be a local eosiod node that connects to the public testnet)
After each interaction using eosioc to communicate with the testnet, record the transaction_id that is returned.
Your eosioc will either connect with node1 or node2. Steps #1 - #7 can be performed on either node. node1's config.ini file should not have any "filter_on_accounts = ..." lines. node2's config.ini should have "filter_on_accounts = tester1" and "filter_on_accounts = tester11"
All corresponding private keys need to be imported into wallet for below used public keys.

  1. create an account "tester1" (or choose your own name) with different owner and active public keys, using the existing "inita" account
  2. create an account "tester2" (or choose your own name) with different owner and active public keys, using the existing "inita" account
  3. create an account "tester11" (or choose your own name) with different owner and active key pair, using the existing "inita" account
  4. create an account "tester21" (or choose your own name) with the same owner key pair used for "tester1” and the same active key pair used for "tester2”, using the existing "inita" account
  5. transfer 100 EOS from "inita" to "tester1"
  6. transfer 200 EOS from "inita" to "tester2"
  7. transfer 100 EOS from "tester2" to "tester11"
  8. run eosioc multiple times passing in ”get transaction " followed by the transaction_ids for Replace operations with messages #1-Advanced Permission Hierarchy  #7 above, and verify the returned transaction contains data consistent with the corresponding activity when connecting to node1, and should only return the transactions from Implement transaction cycles/threads #5 and Advanced Permission Hierarchy  #7 for node2
  9. run eosioc passing in "get accounts ” followed by the owner public key for "tester1" and verify that an array with "tester1" and "tester21" is returned for node1, and nothing is returned for node2
  10. run eosioc passing in "get accounts ” followed by the active public key for "tester1" and verify that an array with just "tester1" is returned for node1 and nothing for node2
  11. run eosioc passing in "get accounts ” followed by the owner public key for "tester2" and verify that an array with just "tester2" is returned for node1 and nothing is returned for node2
  12. run eosioc passing in "get accounts ” followed by the active public key for "tester2" and verify that an array with "tester2" and "tester21" is returned for node1 and nothing is returned for node2
  13. run eosioc passing in "get accounts ” followed by the owner public key for "tester11" and verify that an array with just "tester11" is returned for node1 and nothing is returned for node2
  14. run eosioc passing in "get accounts ” followed by the active public key for "tester11" and verify that an array with just "tester11" is returned for node1 and nothing is returned for node 2
  15. run eosioc passing in "get servants " followed by "inita" and verify an array with "tester1" and "tester2" is returned for node1 and "tester1" for node2
  16. run eosioc passing in "get servants " followed by "tester1" and verify nothing is returned for node1 and node2
  17. run eosioc passing in "get servants " followed by "tester2" and verify nothing is returned for node1 and node2
  18. run eosioc passing in "get servants " followed by "tester11" and verify nothing is returned for node1 and node2
  19. run eosioc passing in "get servants " followed by "tester21" and verify nothing is returned for node1 and node2
  20. run eosioc passing in "get transactions " followed by "inita” and verify that the transactions returned by Port to AppBase #6, Implement transaction cycles/threads #5, Implement Last Irreversible Block, et al #4, Remove maintenance interval #3, Transactions should Explicitly Declare Required Authority Level #2, and Replace operations with messages #1 are returned in an array (in that order) for node1, and only Implement transaction cycles/threads #5 for node2
  21. run eosioc passing in "get transactions " followed by "tester1” and verify that the transactions returned by only Implement transaction cycles/threads #5 are returned in an array by node1 and node2
  22. run eosioc passing in "get transactions " followed by "tester2” and verify that the transactions returned by Advanced Permission Hierarchy  #7 and Port to AppBase #6 are returned in an array (in that order) for node1 and only Advanced Permission Hierarchy  #7 for node2
  23. run eosioc passing in "get transactions " followed by "tester11” and verify that the transaction returned by only Advanced Permission Hierarchy  #7 are returned in an array for node1 and node2
  24. run eosioc passing in "get transactions " followed by "tester21” and verify that an empty array is returned by node1 and node2
  25. run eosioc passing in "get transactions " followed by "inita 1 2” (start at seq Replace operations with messages #1 and returns 2) and verify that the transactions returned by Implement transaction cycles/threads #5 and Implement Last Irreversible Block, et al #4 are returned in an array (in that order) for node1 and an empty array for node2
@blockone-syncclient
Copy link
Author

➤ Brian Johnson commented:

[~bart.wyatt] [~kevin.heifner] I'm planning to just return the signed_transaction, and not worry about the outputs that used to be returned also for get_transaction.

@blockone-syncclient
Copy link
Author

➤ Brian Johnson commented:

Everything is ported over to eos-noon, but need to test with new launcher and eosioc merges, so that I can verify that everything is working.

@wanderingbort
Copy link
Contributor

I'm going to close this as the ticket for initial work, if we add features we can do so in a new ticket

@coreylederer coreylederer added this to the Q1, 2018 milestone Mar 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants