BribeFi is Safe multisig module that allows governance participants to bribe holders for making votes on their behalf
BribeFi is a Safe multisig module that allows governance participants to bribe holders to make votes on their behalf.
Governance participants want to bribe holders for casting votes. There are already several implementations of governance bribes, for example, Compound DAO. BribeFi is different in a few ways:
DAOs may need BribeFi for 2 main reasons:
Holders of any DAO that is using Snapshot.org can use BribeFi. DAOs include, but are not limited to Uniswap DAO, Safe DAO, AAVE DAO, Gnosis DAO, Optimism DAO, APECoin DAO, 1Inch DAO, etc.
Moreover, BribeFi architecture may support NFT DAOs like Nouns DAO.
The BribeFi module takes 1% commission on bribes. 50% of the commission might be distributed to a referral program to create additional incentives to promote the module.
In the future, token pools may be implemented. They will allow low-bank users also to get yield on their governance tokens. Subscription for voting power on demand feature may be also implemented in the future.
BribeFi is a Safe multisig module. It has a function for creating a bid for a casting vote transaction. The holder can accept any bid he wants, the same transaction he accepts the bid - a vote is casted on-chain. ADD architecture Image
Site: https://bribefi.xyz Submission page: add link Github: https://github.com/lourenc/bribefi-core
ExampleERC20 deployed to: 0x5FbDB2315678afecb367f032d93F642f64180aa3
BribeP2P deployed to: 0xe7f1725E7734CE288F8367e1Bb143E90bb3F0512
BribeFI is a decentralized peer-to-peer platform that enables users to exchange signed data in return for payment. Built for EVM blockchains, the smart contract utilizes the ERC20 token standard and implements the OpenZeppelin Ownable, IERC1271, and IERC20 interfaces.
Users can initiate a signing request by calling the pushSigningRequest function with a specified block number, data to be signed, and the amount of payment they are offering. The function verifies that the user has sufficient funds and allowance for the token transfer, then creates a new signing request object with a unique identifier.
The contract owner can review the pending signing requests and accept or reject them by calling the acceptSigningRequest or rejectSigningRequest function, respectively. If the signing request is accepted, the function verifies the signed data against the original data and pays the offer amount to the counterparty. If the signing request is rejected, the function refunds the offer amount to the counterparty.
The signing request object includes the status of the request, the counterparty's address, the offer amount, the block number, and the data to be signed. The status can be one of Pending, Accepted, or Rejected. The ECDSA library is used for cryptographic signing and verification.
Overall, BribeFI provides a secure and transparent way for users to exchange signed data for payment without the need for intermediaries.