Integration with Yiimp #10

Closed
opened 2022-01-12 05:58:57 +01:00 by roylee17 · 1 comment
roylee17 commented 2022-01-12 05:58:57 +01:00 (Migrated from github.com)

Integration with Pool software - Yiimp

  • 1. Stratum seems have issues connecting to lbcd/lbcwallet via TLS

  • 2. lbcd does not support blocknotify as a builtin function.

  • 3. Stratum complains about Lbry error getblocktemplate

Integration with Pool software - [Yiimp](https://github.com/tpruvot/yiimp.git) - [x] 1. Stratum seems have issues connecting to lbcd/lbcwallet via TLS - [x] 2. lbcd does not support blocknotify as a builtin function. - [x] 3. Stratum complains about `Lbry error getblocktemplate` - #12 - #13
roylee17 commented 2022-06-11 06:53:51 +02:00 (Migrated from github.com)

Updates:

We have successfully mined the first block with lbcd & lbcwallet on lbrypool.net at block 1173833.

A pending (but non-blocking) issue related to the legacy getinfo RPC, which has been removed on lbrycrdand bitcoind in favor of getblockchaininfo, getnetworkinfo, and getwalletinfo. Yiimp fails to parse the results of get**info returned by lbcd, so we have to fallback to use the legacy getinfo, which is still available in lbcd.

Close the Yiimp integration epic issue here, and open another issue make sure get**info on lbcd conforms to the latest spec.

Updates: We have successfully mined the first block with `lbcd & lbcwallet` on [lbrypool.net](https://lbrypool.net/site/mining) at block [1173833](https://explorer.lbry.com/blocks/1173833). A pending (but non-blocking) issue related to the legacy `getinfo` RPC, which has been removed on **lbrycrd**and **bitcoind** in favor of `getblockchaininfo`, `getnetworkinfo`, and `getwalletinfo`. **Yiimp** fails to parse the results of `get**info` returned by **lbcd**, so we have to fallback to use the legacy `getinfo`, which is still available in **lbcd**. Close the Yiimp integration epic issue here, and open another issue make sure `get**info` on **lbcd** conforms to the latest spec.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbcd#10
No description provided.