如何使用rpc解析操作端点

Question

如何使用rpc解析操作端点

8

178 2019-05-07

我正在尝试查询RPC 解析操作端点

RPC文档仅声明此端点Parse operations,我似乎找不到在网络上使用它的示例.

我的目标是基本上扭转伪造端点以便从十六进制编码操作中获取JSON.

这是我用来查询端点的步骤:

伪造操作

查询:

 POST
https://alphanet-node.tzscan.io/chains/main/blocks/head/helpers/forge/operations

身体:

 {
    "branch": "BLpcXF8ADJbGuyUKNv7TypXRd5rqnoPn3PMqJLNBeRSr4VFeUuK",
    "contents": [
        {
            "kind": "transaction",
            "source": "tz1NfEiS2uJsX43vowNjau5pdqg3Nvy8whvc",
            "destination": "KT1Ec3jNXyxyA54nezwcjGDRoutECJCQjpya",
            "fee": "1274",
            "counter": "86610",
            "gas_limit": "10100",
            "storage_limit": "0",
            "amount": "5060726"
        }
    ]
}

响应:

 "92122a7e654cdff09e22a7be1b7d41bd279ffa197a0137e6fea0d3ed3ce95fc00800002122d44d997e158c36c60649d198c4175dad425efa09d2a405f44e00f6f0b40201420eaa410ac21addf427211cddd6115cba385a940000"

现在尝试反转伪造操作

查询:

 https://alphanet-node.tzscan.io/chains/main/blocks/head/helpers/parse/operations

身体:

 {
    "operations": [
        {
            "data": "92122a7e654cdff09e22a7be1b7d41bd279ffa197a0137e6fea0d3ed3ce95fc00800002122d44d997e158c36c60649d198c4175dad425efa09d2a405f44e00f6f0b40201420eaa410ac21addf427211cddd6115cba385a940000",
            "branch": "BLpcXF8ADJbGuyUKNv7TypXRd5rqnoPn3PMqJLNBeRSr4VFeUuK"
        }
    ]
}

响应:

 [
    {
        "kind": "branch",
        "id": "proto.003-PsddFKi3.operation.cannot_parse"
    }
]

解析操作终结点是否确实在按照我的期望进行? 如果是这样,应该如何查询该端点以反转伪造端点?

I am trying to query the RPC parse operation endpoint

The RPC documentation only states that this endpoint Parse operations and I can't seem to find example of how to use it on the web.

What I am aim to do is basically reverse what the forge endpoint does in order to get the JSON from an hex encoded operation.

Here are the step I am using to query the endpoint:

Forge operation

Query:

POST
https://alphanet-node.tzscan.io/chains/main/blocks/head/helpers/forge/operations

Body:

{
    "branch": "BLpcXF8ADJbGuyUKNv7TypXRd5rqnoPn3PMqJLNBeRSr4VFeUuK",
    "contents": [
        {
            "kind": "transaction",
            "source": "tz1NfEiS2uJsX43vowNjau5pdqg3Nvy8whvc",
            "destination": "KT1Ec3jNXyxyA54nezwcjGDRoutECJCQjpya",
            "fee": "1274",
            "counter": "86610",
            "gas_limit": "10100",
            "storage_limit": "0",
            "amount": "5060726"
        }
    ]
}

Response:

"92122a7e654cdff09e22a7be1b7d41bd279ffa197a0137e6fea0d3ed3ce95fc00800002122d44d997e158c36c60649d198c4175dad425efa09d2a405f44e00f6f0b40201420eaa410ac21addf427211cddd6115cba385a940000"

Now trying to reverse the forge operation

Query:

https://alphanet-node.tzscan.io/chains/main/blocks/head/helpers/parse/operations

Body:

{
    "operations": [
        {
            "data": "92122a7e654cdff09e22a7be1b7d41bd279ffa197a0137e6fea0d3ed3ce95fc00800002122d44d997e158c36c60649d198c4175dad425efa09d2a405f44e00f6f0b40201420eaa410ac21addf427211cddd6115cba385a940000",
            "branch": "BLpcXF8ADJbGuyUKNv7TypXRd5rqnoPn3PMqJLNBeRSr4VFeUuK"
        }
    ]
}

Response:

[
    {
        "kind": "branch",
        "id": "proto.003-PsddFKi3.operation.cannot_parse"
    }
]

Is the parse operation endpoint really doing what I expect? If so how should this endpoint need to be queried to reverse the forge endpoint?

1 个回答

投票数

Tom · Accepted Answer · 2019-05-10

5

2019-05-10

问题在于/parse/operations需要签名的操作.您可以只在末尾添加64个零字节:

 {
    "operations": [
        {
            "data": "0800002122d44d997e158c36c60649d198c4175dad425efa09d2a405f44e00f6f0b40201420eaa410ac21addf427211cddd6115cba385a94000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
            "branch": "BLpcXF8ADJbGuyUKNv7TypXRd5rqnoPn3PMqJLNBeRSr4VFeUuK"
        }
    ]
}

请注意,如果您信任这些RPC的输出,则您信任节点.

还请注意,/parse/operations的" check_signature"选项无效,如您将其设置为true所见...

The problem is that /parse/operations expects signed operations. You can just add 64 zero bytes to the end:

{
    "operations": [
        {
            "data": "0800002122d44d997e158c36c60649d198c4175dad425efa09d2a405f44e00f6f0b40201420eaa410ac21addf427211cddd6115cba385a94000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
            "branch": "BLpcXF8ADJbGuyUKNv7TypXRd5rqnoPn3PMqJLNBeRSr4VFeUuK"
        }
    ]
}

Be warned that if you trust the output of these RPCs, you are trusting the node.

Also notice that the "check_signature" option for /parse/operations has no effect, as you can see by setting it to true...

原文
Tom

您能举一个完整的例子,先进行伪造,签名然后解析吗?即使加上0后,我仍然无法解析工作.

Could you give a complete example of this, doing a forge, sign, then parse? Even after adding the 0's, I still cannot get parse to work.
- 0
- 2019-09-17
- utdrmac
我想问题+答案给出了一个完整的例子,我可能会在以后的某个时间扩展答案.快速检查两次:您添加了128个零(=64个零字节)?您从伪造中剥离了前32个字节(64个字符),这是分支/块哈希?(我没有在回答中提及这一点.)

I guess the question + answer gives a complete example, I might expand the answer sometime later. Two quick checks: You added 128 zeros (= 64 zero bytes)? You stripped off the first 32 bytes (64 characters) from forge, which are the branch / block hash? (I failed to mention that in my answer.)
- 0
- 2019-09-18
- Tom
上面的示例都涉及转移操作,我正在尝试对背书进行解码.它们有些不同.阅读其他文章和ocaml代码后,我可以使它工作.谢谢

The above examples all deal with transfer operations and I was trying to decode an endorsement. They are a bit different. I was able to get it working after reading some other posts and ocaml code. Thanks
- 0
- 2019-09-19
- utdrmac