Goal: Node Operator incentive and uptime control mechanism

[zolotokrylin]

Spec

Problem:

• Problem: Smart Contract Onchain is not ready #718
• Problem: TN Reward Infrastructure is not designed #719
• truflation/tsn-data-provider#314
• truflation/tsn-data-provider#315

Blocked by

• Goal: More performant architecture with Kwil v0.10 #673

[zolotokrylin]

@brennanjl, as discussed today on the phone, could you please help here to come up with the optimal solution? Feel free to propose one.
P.S. As you mentioned, Symbiotic is not ready to be used in production.

@srust99 FYI/R.

[zolotokrylin]

@brennanjl,

1. could you please include all the information you discussed with Cameron and Stefan in the Spec document (see description of this issue)?
2. ⚠️ Let's keep this issue only scoped to Node Operator incentive mechanism.

[zolotokrylin]

I'm digging in now to begin planning how we can attack this.

Let's attack it using this process:

1. produce the Spec doc. Put in the doc all the ideas and requirements you gathered from Stefan and Cameron, including your own thoughts.
2. iterate over the doc until all stakeholders agree.
3. proceed with the development

[zolotokrylin]

@brennanjl, when can we expect the first version of the Spec, please?

[brennanjl]

@zolotokrylin I should have next steps by EOD Wednesday. I have been digging into technical details to figure out how this can be implemented, and still have a bit more work to do.

[zolotokrylin]

@brennanjl replied to your questions in the spec. Please continue in the document. Thanks!

[brennanjl]

@zolotokrylin I have added more information to the spec, and linked Kwil's working spec that outlines what our team will need to do to enable node operator rewards.

We are still writing the specs, but we have broken the project down into 4 sub-projects (all will be handled by Kwil). We are also hiring a fulltime contractor (at our expense) to help speed up the implementation of this project specifically, because we know it is a high priority.

Once our team has settled on our approach (which we are outlining here), we will follow up with what TSN needs to design specifically for your own rewards.

This is our top priority (I am personally spending all day, every day on this until it is done), so we should have more details soon.

[zolotokrylin]

@brennanjl, do you guys have any progress, and do you have any ETA in mind?

[brennanjl]

@zolotokrylin Yes, will revert on this today

[brennanjl]

@zolotokrylin There are two documents relevant to this.

The first is the spec, which is what Kwil is using internally. It is actually an overview that links to two more in-depth specs, which specify the extensions/adapters and smart contracts that are needed to implement rewards. This is conceptually similar to what I linked above, but has more details fledged out and is currently being implemented.

The second is the milestones for these, which gives and estimate of engineering days, as well as order of priorities and blockers.

[zolotokrylin]

@brennanjl, can you please permit me to comment? I have some questions I could ask directly in the docs.

[brennanjl]

@zolotokrylin you should be able to comment now. Let me know if you still cannot.

[zolotokrylin]

Thank you. We are reviewing it. I will get back to you with feedback.

[markholdex]

Hey @MicBun please review the docs and suggestions and provide your feedback based on the business requirements we discussed. Appreciate it 🙏

[zolotokrylin]

@MicBun please move your comments into spec doc and ping us here. Thanks

[MicBun]

you should be able to comment now. Let me know if you still cannot.

Hi @brennanjl, I can't leave a comment on Kwil Rewards Outline document. Can I leave some comment on it?

[MicBun]

Hi @zolotokrylin, @brennanjl, @brennanjl
I left some comments in the docs.

[brennanjl]

Everyone should have access. I also changed the link to this, which is a slightly more up-to-date version that includes some security improvements.

[MicBun]

Everyone should have access. I also changed the link to this, which is a slightly more up-to-date version that includes some security improvements.

Alright, thanks! @brennanjl, I leave some comments regarding the example in the docs.

[zolotokrylin]

@brennanjl

1. I left you a comment in the doc. Please check.
2. what's the ETA with your part of the infra?

[brennanjl]

@zolotokrylin will take a look today. Apologies, I am at another conference.

@zolotokrylin our ETA is still probably a couple months. The milestones get us to a prototype, but it will be a bit longer to get that into production.

[zolotokrylin]

@brennanjl did you have a chance to look into my comments?
@markholdex let's set up a call and push this forward on all sides.

[MicBun]

@zolotokrylin looks like it automatically got unassigned because of the repository transfer. I couldn't edit the assignee.

[brennanjl]

@zolotokrylin yes I responded to your comment.

[zolotokrylin]

@brennanjl @srust99 We have booked a call to discuss this issue and breakthrough.
cc: @markholdex

[markholdex]

log of the call:

• We will be waiting for the new Kwil architecture to be completed before we begin working on billing and node operator incentives.
• Goal: More performant architecture with Kwil v0.10 #673

The reason for that is the built-in billing mechanism that will come with the new architecture that will allow us to reward node operators, data providers, and bill consumers.

• We can already track data consumption with KGW through logs. But that information is not stored on-chain on the Truf Network.

cc: @srust99 @zolotokrylin @Jarryd-pretorius @brennanjl