SRI Translator Proxy compatibility matrix

[plebhash]

SRI Provides a Translator Proxy (tProxy). It translates SV1 traffic into SV2. It is a key component for SV2 adoption in the Mining Industry.

Different SV1 firmware flavors can result in different edge cases. It is strategically important for SRI tProxy to cover the most popular SV1 firmwares in the industry.

---

@GitGab19 and I will spend 3 weeks in Thailand for a Residency in BOB Space (Dec 1-20)

@rrybarczyk might join us for a few days (week?)

we will have access to a wide range of SV1 Mining Devices there

we should take that opportunity to battle test SRI tProxy

as an outcome of this effort, I propose that we add a matrix of device support to roles/translator/README.md

something like this:

Mining Device	Control Board	Firmware	tProxy support ok? if not, issue tracking compatibility bug	validated by
S19j	Braiins BCB 100	BOS v24.08.1	✅	@ foo
S19j	Mara UCB 2100	Mara OS xxx	✅	@ bar
S21 Pro	Bitmain Stock	Antminer stock 202408281552	✅	@ foo
WhatsMiner M30+			❌ #1173	@ bar

if the number of compatibility bugs is too big for us to be able to fix everything during the time we spend there, we will need to make compromises, which will mostly consist of:

• which models deserve priority
• how can we encourage the community to submit PRs that will help fix the ones we did not have the bandwidth to fix during the residency

[pavlenex]

We did have a matrix with our early release (way pre 1.0.0), but a lot has changed, and I am unable to locate that doc in our drive.

I am not sure if battle testing is a proper term here, but having a compatibility matrix would help. I think the end-goal here is to test on as many miners as you have and also set up a system where any community member can contribute to. An easy way to keep a track of compatibility could be a GitHub issue which has an owner that maintains, and testers could simply leave a comment once they test with a particular device/firmware. One example of how we conducted tests with uppercase Bech32 on BTCPay. btcpayserver/btcpayserver#2110

Having a tracker issue would not only help with an easy way to provide feedback, but also help with cross-posting in manufacturers repos and advocate for compatibility.

[plebhash]

An easy way to keep a track of compatibility could be a GitHub issue which has an owner that maintains, and testers could simply leave a comment once they test with a particular device/firmware.

that's a better path indeed

we should just keep editing this issue description as we make progress on this effort

this dynamic approach is probably easier than having to approve and merge multiple PRs that are modifying roles/translator/README.md