Closed enobayram closed 1 year ago
I have tested this PR by running a chainweb-data
instance from it against a mainnet01
and a fast-development
node. It works without any issues in server
and fill
modes.
In addition to testing this PR on mainnet01
and fast-development
, I've also double-checked that the cut
and payload/outputs
endpoints affected by this PR are unconditionally served on the Service API, see:
This PR replaces all p2p endpoint requests with service endpoint requests avoiding the need to have a p2p configuration. This simplifies
chainweb-data
's command line interface, but more importantly, it avoids depending on CW-N's p2p endpoint, which is supposed to be for peer to peer communication only and is subject to backwards-incompatible changes.In particular, this PR moves the following requests to the service endpoint:
GET <node-endpoint>/chainweb/0.0/<network-id>/cut
GET <node-endpoint>/chainweb/0.0/<network-id>/chain/<chain-id>/payload/<block-hash>/outputs