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

get_block: undocumented field "logs" #60

Open
PawelPodkalicki opened this issue Jun 7, 2018 · 2 comments
Open

get_block: undocumented field "logs" #60

PawelPodkalicki opened this issue Jun 7, 2018 · 2 comments
Labels
Backlog Bug Something isn't working

Comments

@PawelPodkalicki
Copy link
Member

After node status change (set_node_status, unset_node_status) in get_block response appears logs field. Sample below

	"logs": [{
			"type": "5",
			"name": "set_node_status",
			"bbank": "2",
			"status": "1048576",
			"atxid": "0001000000870001"
		}
	],

From my observation:

  • type==5 is for set, type==6 is for unset,
  • bbank is node which status is changed,
  • atxid is tx.id of node status change transaction,
  • size of logs array never exceeds 1, new change overwrites old one.

Does it need to be included in wiki or will be deleted from get_block response?

@PawelPodkalicki PawelPodkalicki added Icebox Question Everything You always wanted to know labels Jun 7, 2018
@PawelPodkalicki
Copy link
Member Author

If during one block, multiple change requests are sent, log array has more than one entry.

@PawelPodkalicki PawelPodkalicki changed the title get_block: undocumented field "log" get_block: undocumented field "logs" Aug 13, 2018
@PawelPodkalicki
Copy link
Member Author

After create node 0004 by account 0002-00000000 following entry was present:

    "logs": [
        {
            "type": "7",
            "name": "create_node",
            "auser": "0",
            "bbank": "4",
            "atxid": "0002000000020001"
        }
    ]

@m-pilarczyk m-pilarczyk added Backlog Bug Something isn't working and removed Icebox Question Everything You always wanted to know labels Jun 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backlog Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants