PFK Rewards
Round 6
@Merkletree#5422
15000
15k KEEP
Round 5
@Merkletree#5422
10000
James had a huge soft spot for beacon applications (http://keeprandom.top/)
Introduce yourself
Hey, guys! I’m Merkletree, a crypto fanatic.
Nodes
0x774c31762c54c1922249eaef8c97e722ad79e6c5
Contribution
31.10.2020
Here is my submission PFK for October:
1.I modified the lottery dapp Pooltogether using keep.random as a random source.
Pooltogether is a protocol for no-loss money games powered by Ethereum. Here is my code: https://github.com/laogandie-code/pool-together
2.I have been running my Beacon and ECDSA nodes
30.09.2020
1. http://keeprandom.top/ I built a keep.random based on keep random beacon. Everyone can use my tool to get true randomness from random beacon in a trustless way. To make it easier to use, I made my tool into an npm package, which has been downloaded over 200 times since it was released!
https://www.npmjs.com/package/keep.random
The meaning of this service is that the user cannot call the random value directly via the random beacon, and the random value of the random beacon can only be returned to another smart contract, rather than directly to the user.
You can check out more details here:
In the next step, I am thinking of using KEEP as a way of paying for random numbers, not just ETH. In the meantime, I'll be building more apps based on keep.random.
Here is my submission PFK for October:
1.I modified the lottery dapp Pooltogether using keep.random as a random source.
Pooltogether is a protocol for no-loss money games powered by Ethereum. Here is my code: https://github.com/laogandie-code/pool-together
2.I have been running my Beacon and ECDSA nodes
30.09.2020
1. http://keeprandom.top/ I built a keep.random based on keep random beacon. Everyone can use my tool to get true randomness from random beacon in a trustless way. To make it easier to use, I made my tool into an npm package, which has been downloaded over 200 times since it was released!
https://www.npmjs.com/package/keep.random
The meaning of this service is that the user cannot call the random value directly via the random beacon, and the random value of the random beacon can only be returned to another smart contract, rather than directly to the user.
You can check out more details here:
- https://github.com/laogandie-code/KeepRandom/blob/master/README.md
- https://discordapp.com/channels/590951101600235531/590951101600235533/759406955546017833
In the next step, I am thinking of using KEEP as a way of paying for random numbers, not just ETH. In the meantime, I'll be building more apps based on keep.random.
