roles
roles copied to clipboard
bisq-network
Relay operator for mobile notifications
Running the relay node used for mobile notifications.
Primary owner: @devinbileck
2019.04 report
I have setup and transferred ownership of the jtboonrvwmq7frkj.onion relaynode from @ManfredKarrer (https://github.com/bisq-network/bisq/pull/2770).
While attempting to setup/run the relay node, I was encountering Error while calling FCM backend service when relaying Android notifications and no Android notifications were being relayed. However, iOS notifications work fine.
Unfortunately, this issue wasn't identified until after I had already made the transition and my node was the primary relay. As a result, for several hours on April 24/25 Android notifications were not being relayed. During my testing prior to the transition, I had just tested iOS notifications and assumed the relay was functioning correctly since I did not have access to an Android device at the time to verify.
At this point, the issue seems to be due to compiling under the new mono repo using Java 10. Whereas using the old bisq-relay repo and compiling with Java 8, Android notifications work fine. So for now, my relay is using the old repo with Java 8.
An issue has been entered for this, see https://github.com/bisq-network/bisq/issues/2791.
Expenses incurred for the month (USD):
- $10 for server (1 CPU, 2GB)
Note: Although the transition did not occur until towards the end of the month, my server was running since the beginning of the month in preparation/anticipation of the transition.
/cc bisq-network/compensation#270
2019.05 report
Running 1 relaynode.
- jtboonrvwmq7frkj.onion
No issues to report this month.
No maintenance required this month.
Expenses incurred for the month (USD):
- $10 for server (1 CPU, 2 GB RAM)
/cc bisq-network/compensation#295
Cycle 3 report
Summary
Running 1 relay node for mobile notifications, nothing notable happened this month.
- jtboonrvwmq7frkj.onion
Issues Encountered
No issues encountered this month.
Maintenance Performed
No maintenance performed this month.
Expenses Incurred
Expenses incurred for the month (USD):
- $10 for server (1 CPU, 2 GB RAM)
/cc bisq-network/compensation#309
Cycle 4 report
Summary
Running 1 relay node for mobile notifications, nothing notable happened this month.
- jtboonrvwmq7frkj.onion
Issues Encountered
No issues encountered this month.
Maintenance Performed
No maintenance performed this month.
Expenses Incurred
Expenses incurred for the month (USD):
- $10 for server (1 CPU, 2 GB RAM)
/cc bisq-network/compensation#326
Cycle 5 report
Summary
Running 1 relay node for mobile notifications, nothing notable happened this month.
- jtboonrvwmq7frkj.onion
Issues Encountered
No issues encountered this month.
Maintenance Performed
No maintenance performed this month.
Expenses Incurred
Expenses incurred for the month (USD):
- $10 for server (1 CPU, 2 GB RAM)
/cc bisq-network/compensation#353
Cycle 6 report
Summary
Running 1 relay node for mobile notifications.
- jtboonrvwmq7frkj.onion
Issues Encountered
On Sept 12th, iOS notifications stopped working due to an expired Apple push certificate. I was made aware of the issue from this forum post. It took a couple days to resolve the issue, but I acquired and deployed a new certificate with the help of @joachimneumann who manages the app and certificates. Apparently an email was received from Apple 30 days prior to it expiring, but it was not acted upon. The new certificate will expire on 2020/10/13, so hopefully we will act to renew it in time before it expires again.
Maintenance Performed
No maintenance performed this month, aside from updating the Apple push certificate.
Expenses Incurred
Expenses incurred for the month (USD):
- $10 for server (1 CPU, 2 GB RAM)
/cc bisq-network/compensation#378
Cycle 7 report
Summary
Running 1 relay node for mobile notifications.
- jtboonrvwmq7frkj.onion
Issues Encountered
No issues encountered.
Maintenance Performed
No maintenance performed.
Expenses Incurred
Expenses incurred for the month (USD):
- $10 for server (1 CPU, 2 GB RAM)
/cc bisq-network/compensation#400
Cycle 8 report
Summary
Running 1 relay node for mobile notifications.
- jtboonrvwmq7frkj.onion
Issues Encountered
None.
Maintenance Performed
None.
Requested Compensation
- 10 USD for server costs (1 CPU, 2 GB RAM)
- 50 USD to ensure 24/7 trouble-free operation
Total: 60 USD
/cc bisq-network/compensation#437
Cycle 9 report
Summary
Running 1 relay node for mobile notifications.
- jtboonrvwmq7frkj.onion
Issues Encountered
None.
Maintenance Performed
None.
Requested Compensation
- 10 USD for server costs (1 CPU, 2 GB RAM)
- 50 USD for maintenance/operational costs
Total: 60 USD
/cc bisq-network/compensation#472
Cycle 10 report
Running 1 instance. Lately I have heard iOS users are encountering issues with the mobile app being unable to decrypt messages, in addition to issues around pairing. While I dont think this is due to the relay, I am still planning to investigate the issue.
/cc bisq-network/compensation#481
Cycle 11 report
Running 1 instance. I have not had time yet to investigate the above mentioned issue.
/cc bisq-network/compensation#512
Cycle 22 report
Running 1 instance. I just realized the iOS certificate has expired again, so that means iOS users are not receiving notifications. As Joachim is no longer active with Bisq, I will potentially need to find a replacement or take ownership myself. I had considered taking ownership in the past, but the major reason holding me back is that I don’t have a Mac so am unable to setup a dev environment, plus the fact that obtaining a certificate requires an annual subscription to Apple.
/cc bisq-network/compensation#797
Cycle 23 report
Running 1 instance. I have decided to take ownership of the apps. I am in the process of transferring ownership within the Apple app store and hope to be done early next week. Then I will focus on transfering the Android app.
/cc bisq-network/compensation#812
Cycle 24 report
Running 1 instance. Ownership of the iOS and Android apps have been transferred to myself. Going forward, I will now be able to update/maintain the iOS push notification certificate myself.
/cc bisq-network/compensation#840
Cycle 26 report
I deployed a new relay node using a Tor v3 address. I will keep the old v2 node running likely for at least the next couple months until all users have updated to a newer Bisq with this change. Ref: https://github.com/bisq-network/bisq/pull/5593
/cc bisq-network/compensation#872
Cycle 27 report
Running 2 instances (Tor v2 and Tor v3). The Tor v2 relay is still receiving push messages, so I will continue to leave it running.
/cc bisq-network/compensation#894
Cycle 28 report
Running 2 instances (Tor v2 and Tor v3). The Tor v2 relay is still receiving push messages from a few Bisq clients < 1.7.2, so I will continue to leave it running. Will likely be able to officially retire it October 15th, 2021 when Tor v2 is no longer supported.
/cc bisq-network/compensation#907
Cycle 29 report
Running 2 instances (Tor v2 and Tor v3). The Tor v2 relay is still receiving push messages from a few Bisq clients < 1.7.2, so I will continue to leave it running. Although Tor v2 should now be no longer officially supported as of October 15th, I don't mind leaving it running for a while longer as long as people are using it and it still works.
/cc bisq-network/compensation#929
Cycle 30 report
Running 2 instances (Tor v2 and Tor v3). The Tor v2 relay is still receiving push messages from a few Bisq clients < 1.7.2, so I will continue to leave it running. Although Tor v2 should now be no longer officially supported as of October 15th, I don't mind leaving it running for a while longer as long as people are using it and it still works.
/cc bisq-network/compensation#943