oskarth
oskarth
Research private reputation mechanism for finding good service nodes for resource-restricted devices
^ @staheri14 @jm-clius @barryWhiteHat I think this is worth look into and I'd personally like to push for it. I think it'd go nicely with Discovery, and it'd mean shared...
Research private reputation mechanism for finding good service nodes for resource-restricted devices
I've started looking into this. First step is more things that it shares with other mechanisms like RLN, e.g. the identity tree. See comments in #research - will likely use...
Research private reputation mechanism for finding good service nodes for resource-restricted devices
There are two roles in Unirep: attesters and users. While an entity could possess both roles, a question that needs to be answered is: Why is notion of attention and...
Research private reputation mechanism for finding good service nodes for resource-restricted devices
That might work! Have to think about it a bit more. In general, the goal should be to make attestations cheap. For our use case, an attester would attest to...
Research private reputation mechanism for finding good service nodes for resource-restricted devices
Brief updated: This issue has morphed a bit into: https://github.com/vacp2p/research/issues/91 https://forum.vac.dev/t/on-zk-gas-costs-and-scaling-solutions-today-tomorrow-and-beyond/104 https://github.com/vacp2p/research/issues/93 We have gotten more clarity on the first two, whereas the third is being investigated
Research private reputation mechanism for finding good service nodes for resource-restricted devices
Priority right now is RLN and harmonizing ZK interface (https://github.com/vacp2p/zerokit) so we can get RLN testnet working for both nim-waku and js-waku. We'll be able to revisit this shortly. Unassigned...
Hi everyone! I finally wrote-up my thoughts on how to approach this: https://github.com/oskarth/mopro/issues/22 If anyone wants to work on this and wants help with using mopro I'd be happy to...
This would require a spec change right? If so we should have an issue and discussion/decision in RFC repo
@s1fr0 what's the state of this issue? cc @rymnc
Same issue here. Seems like this issue is rather old with no response. Is this library still being maintained?