01
Submit
A customer creates a claim with an amount. The contract records the customer, amount, and Submitted state.
submitClaim(amount)FINTECH / INSURTECH / SMART CONTRACTS
Claims, with a
clear record.
An Ethereum-based claim manager that brings eligibility, approval, and settlement into one auditable on-chain workflow.
CLAIM_MANAGER.sol● DEPLOYED LOGIC
CONTRACT BALANCE10.00 ETHfunded at deployment
01SUBMITTEDcustomer claim
02APPROVEDadmin + KYC
03PAIDsettled on-chain
01 / CLAIM WORKFLOW
From first report
to final payment.
A focused smart-contract workflow assigns a clear role to every action. The contract enforces the order; emitted events preserve the record.
02
Verify
The admin performs KYC. The customer can then request approval if the claim exists and the contract has enough funds.
kyc(customer, true)03
Settle
Only the admin can trigger payment. The balance is reduced, the customer receives the claim amount, and the state becomes Paid.
triggerPayment(customer)02 / CONTRACT DESIGN
Rules encoded
as permissions.
The contract separates customer and admin capabilities through interfaces and an onlyAdmin modifier. Claims and KYC records are private mappings exposed through role-aware getters.
CustomersubmitClaim / askApproval / getClaim
can act on own claimAdminkyc / triggerPayment / getCustomerClaim
controls verification + payoutEventsNewClaim / ClaimApproved / ClaimPaid
creates an audit trailSOLIDITY 0.5 → 0.9 / BROWNIE / GANACHE
03 / ENGINEERING NOTES
Small contract.
Useful pattern.
3Explicit claim states
Submitted, Approved, and Paid make the lifecycle easy to inspect.
4Domain events
Claims and state changes can be followed from emitted logs.
1Settlement authority
The admin boundary centralizes KYC and payment permissions.
03 / SMART-CONTRACT THEORY
Why this pattern
works on-chain.
A claim is a state machine: a valid transition is more important than a single database update. Solidity turns business rules into executable permissions, while events create a public history of what changed and when.
Submitted → Approved → Paid makes invalid transitions reject automatically. A customer cannot request approval without a claim, and an administrator cannot pay an unapproved claim.
The onlyAdmin modifier is a capability boundary. It restricts KYC, balance inspection, and settlement to the address established at deployment.
NewClaim, ClaimApproved, and ClaimPaid emit structured logs. Off-chain interfaces can index these events without changing contract state.
The payable contract acts as a simple claim reserve. Before approval, the contract checks that its tracked balance can cover the requested amount.
PRESERVED SOURCE / 2022 REPOSITORY
Built to be inspected.
The original Solidity contract, Brownie deployment script, and test scaffold remain unchanged as historical engineering artifacts.