After signing up, attesters can set the airdrop amount that whoever signs up through the attester, the user can get airdropped positive reputation.
function setAirdropAmount(uint256 amount) external
source:
Airdrop Epoch key
An attester can submit the airdrop attestation to an epoch key with a . The msg.sender should match the attesterId in the publicSignals.
/**
* @dev An attester submit the airdrop attestation to an epoch key with a sign up proof
* publicSignals[0] = [ epoch ]
* publicSignals[1] = [ epochKey ]
* publicSignals[2] = [ globalStateTree ]
* publicSignals[3] = [ attesterId ]
* publicSignals[4] = [ userHasSignedUp ]
* @param publicSignals The public signals of the sign up proof
* @param proof The The proof of the sign up proof
*/
function airdropEpochKey(
uint256[] memory publicSignals,
uint256[8] memory proof
) external payable
Submit Epoch Key Proof
The epoch key proof should be submitted before to get attestation. Then others can verify if the attestation is given to a valid epoch key.
/**
* @dev A user should submit an epoch key proof and get a proof index
* publicSignals[0] = [ globalStateTree ]
* publicSignals[1] = [ epoch ]
* publicSignals[2] = [ epochKey ]
* @param publicSignals The public signals of the epoch key proof
* @param proof The The proof of the epoch key proof
*/
function submitEpochKeyProof(
uint256[] memory publicSignals,
uint256[8] memory proof
) external
import { ReputationProof } from '@unirep/contracts'
const proof = new ReputationProof(
publicSignals,
proof
)
const proofHash = proof.hash(()
Then call the UniRep smart contract to query the proof index
const unirepContract = new ethers.Contract(address, abi, provider)
const index = await unirepContract.getProofIndex(
proofHash
)
source:
source:
An attester can submit the attestation with a proof index. A valid proof is either an , a or a with epoch key being one of the public signals. An attester can also submit attestations through a relayer or not.
It it is from a we should include a fromProofIndex to make sure the attestation is from a valid reputation proof, or the attestation will fail.
source:
source:
A user include a to spend reputation via an attester, the non-zero nullifiers will be processed as a negative attestation, and the spent reputation cannot be re-used.
source:
After the spendReputation event emitted, the reputation will assign a proofIndex. Then the proofIndex can be included in the fromProofIndex of .