Skip to content

Add txid to GetTransactionResult struct#7

Open
jpcummins wants to merge 46 commits intochecksum0:masterfrom
jpcummins:master
Open

Add txid to GetTransactionResult struct#7
jpcummins wants to merge 46 commits intochecksum0:masterfrom
jpcummins:master

Conversation

@jpcummins
Copy link
Copy Markdown

Add txid to GetTransactionResult struct.

jpcummins and others added 30 commits February 16, 2023 20:11
Here we provide a workaround for servers that don't follow the
JSON-RPC 2.0 specification for error objects.

According to the specification, an error should be an object
containing `code`, `message`, and `data` properties
(see: https://www.jsonrpc.org/specification#error_object).
Unfortunately, Electrs returns an error as a string
(see: Blockstream/esplora#453).

We define an error unmarshaling function to handle both types of errors.
It would be usefull to include value that failed unmarshalling in the
debug mode log message.
…shal

Handle error string returned in the JSON-RPC response
Here we add support for WebSocket protocol. With this change the client
will support all connection types defined by the electrum protocol:
`tcp`, `ssl`, `ws` and `wss`.

The WebSocket client initialization expects remote server details to be
provided as URL including a scheme and host, e.g. `tcp://electrum.io:50001`.
The `NewClient` function should be used to initialize the client.
The function resolves transport protocol from the URL.
It supports all four protocols: `tcp`, `ssl`, `ws` and `wss`.
After sending a close message to the server we need to wait for the
response or force the conncetion closure after a timeout.
steveguo2triplea and others added 16 commits December 12, 2023 09:00
The `SubscribeHeadersSingle` function subscribes to receive the header of the
current blockchain tip. Unlike `SubscribeHeaders`, this function only returns
the tip and does not listen for new block headers.

Worth noting that this action still creates a new subscription in the Electrum
server. The protocol does neither support a single-shot request for the
current blockchain tip nor subscription cancellation. Although this limitation
causes a slight resource overhead on the client, it does not cause a memory
leak like the `SubscribeHeaders` method which spawns a goroutine that may hang
on the channel if the caller is no longer pulling from it.
…ders-single

Expose the `SubscribeHeadersSingle` function
This reverts commit ecee726, reversing
changes made to f76fcbf.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants