We have the group token system and contracts on nexa, it would be good to show that these can be used in applications that BU itself use internally, Current system currently relys on google cloud platform and Firebase within the android app, both that and the current votepeerjs have been good resources for this proposal.
The ring signature library uses wasm so this will 100% be utilised
I have contributed to both nifty and wally in the past both being kotlin projects. i have also assisted new team members with coming upto speed with both projects, i was hired via BUIP and no where in my services agreement does it say that i am only allowed to work in Kotlin. My proposal is based on what i think is better for the end user and generally a responsive website should be suffice for this kind of application.
i have been digging through all the code bases for around 12 months and have let solex know that this is a project i have been keen on for quiet some time i have also spoken to the original Votepeer creators about certain parts of the current implementation.
The proposal states that effort and support will be provided to make sure that all current nexa wallets support this new implementation of votepeer.
This is not true, the protocol was made in a relatively short period off BU paid time because it follows similar standards to other crypto DAPPS, i cant speak to it fully as i did not implement it.
i would prefer that members read through the proposal and come to their own conclusion