current implementation contract of USDGLO on Ethereum

current implementation contract of USDGLO on Polygon

All smart contracts versions of Glo can be found at [https://gitlab.com/global-income-coin/usdglo](https://gitlab.com/global-income-coin/usdglo). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

If an impact can be caused to any other asset managed by Global Income Coin that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project. This only applies to Critical impacts.

Glo is a fully backed stablecoin pegged to the US dollar. We're non-profit. Like other stablecoin companies, we earn interest from our reserves. The difference: we give all of it away to reduce extreme poverty. You can generate basic income for people in extreme poverty simply by owning Glo. More Glo adoption means more basic income for more people.

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Permanent freezing of funds

Miner-extractable value (MEV)

Predictable or manipulable RNG that results in abuse of the principal

Protocol insolvency

Temporary freezing of funds for at least 1 hour

Smart contract unable to operate due to lack of token funds

Block stuffing for profit

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Theft of gas

Unbounded gas consumption

Smart contract fails to deliver promised returns, but doesn’t lose value

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-2). This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.

All High and Critical Smart Contract bug  reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required.

Glo requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed are name, address, date and full amount you claim, clearly stated on an invoice. The collection of this information will be done by the project team.

Payouts are handled by the __Glo__ team directly and are denominated in USD. However, payouts are done in __USDC__. 

Glo Dollar

Resources & Documentation