Skip to content

Problem with rpc #1

@breign

Description

@breign
  1. If I use default pay.rpc for datapay.send, the rpc fails with error
    1-default_rpc
    PayloadTooLargeError: request entity too large at readStream (/home/bchsv/prod-2/node_modules/raw-body/index.js:155:17) at getRawBody (/home/bchsv/prod-2/node_modules/raw-body/index.js:108:12) at read (/home/bchsv/prod-2/node_modules/body-parser/lib/read.js:77:3) at jsonParser (/home/bchsv/prod-2/node_modules/body-parser/lib/types/json.js:135:5) at Layer.handle [as handle_request] (/home/bchsv/prod-2/node_modules/express/lib/router/layer.js:95:5) at trim_prefix (/home/bchsv/prod-2/node_modules/express/lib/router/index.js:317:13) at /home/bchsv/prod-2/node_modules/express/lib/router/index.js:284:7 at Function.process_params (/home/bchsv/prod-2/node_modules/express/lib/router/index.js:335:12) at next (/home/bchsv/prod-2/node_modules/express/lib/router/index.js:275:10) at expressInit (/home/bchsv/prod-2/node_modules/express/lib/middleware/init.js:40:5)

  2. if I use my own pay.rpc for datapay.send
    2-my_rpc
    datapay fails with error returning only NodeError

  3. If I use default pay.rpc for datapay.build there is no error from rpc
    screenshot 2019-02-01 at 14 21 01
    but then I need to http send builded tx via my node rpc, and tx gets through successfully
    a80a0a2afc0ba2f76914b26ed98fd9db3e0aedbe3c399c6e3e157f126315332e

my node is available under bitcoinsv.si

if one would like to try directly with node rpc, I can give user & pass.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions