Boofy-Protocol

KO | EN

gitlite — search

#awesome-list #svg #android #gpt #redis #agent #gemini #animation #security #html

(★ 9)

Public repo for the community devs to advance the Boofy protocol.

파일 탐색기

ZIP 다운로드

- boofy-banner.jpg
- boofy-banner.png
- boofy-banner.svg
- IRewardDistributionRecipient.sol
- LPTokenWrapper.sol
- RewardPool.sol
- TokenTimelock.sol
- YFI.sol
- 1_wBNB.sol
- 2_ETH.sol
- 3_LINK.sol
- 4_CREAM.sol
- 5_BNB_BUSD.sol
- 6_BNB_SPARTA.sol
- 0x0dc06716bc1efdb5affd1308302fd45dbc31d09a.sol
- 0x48091c485eb842c86805251a5d68993bf49c90a1.sol
- 0x4dece2b4c14083250f5a68faa18372563d174fea.sol
- 0xeDBf7a30453cf9A63Cca4353b38Ae60AD4E27Bac.sol
- BIFI.sol
- boofyUniswapZap.sol
.gitignore
BOOFY_MIGRATION_NOTICE.md
BOOFY_TEAM.md
CHANGELOG.md
package.json
README.md
ROADMAP.md

# CDN으로 사용하기

jsDelivr

jsDelivr는 공개 GitHub 리포지토리를 별도 설정 없이 CDN으로 즉시 서빙합니다. 버전과 파일을 고르면 웹페이지에 바로 붙일 수 있는 링크와 예시 코드가 만들어집니다.

버전

파일

링크

예시

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

Boofy Protocol is the protocol-level repository for the Boofy DeFi project. It contains protocol architecture, governance/deployment-related source material, and supporting components that sit alongside Boofy App, Boofy API, and Boofy Contracts.

> **Development status:** active migration and protocol definition. Historical upstream deployment identifiers are preserved for traceability but are not automatically valid Boofy production values.

## Project goals

- Define a clear protocol architecture for Boofy.
- Separate historical upstream deployment data from future Boofy deployments.
- Document governance, ownership, and operational assumptions.
- Coordinate protocol changes across App, API, and Contracts.

## Current work

The active protocol tracks are:

1. Protocol naming and documentation cleanup.
2. Deployment-boundary and ownership documentation.
3. Coordination with Boofy Contracts and API configuration.
4. Governance and release-readiness planning.

See [ROADMAP.md](ROADMAP.md) and repository Issues for current work.

## Repository history

Boofy Protocol preserves the upstream development history used as its technical foundation. Historical commits retain their original authorship and timestamps. Current Boofy development is tracked through new commits and issues.

## Team

- **Fan Long** — Co-Founder
- **David Woo** — Developer
- **Tyler Casselman** — Developer
- **Albert Jones** — Developer

See [BOOFY_TEAM.md](BOOFY_TEAM.md).

## Production boundary

Before any production launch, verify contract addresses, token identifiers, governance roles, treasury/multisig configuration, chain parameters, and public endpoints independently.

## Migration notice

See [BOOFY_MIGRATION_NOTICE.md](BOOFY_MIGRATION_NOTICE.md) before treating any historical value as a Boofy deployment value.

## License and attribution

Original upstream attribution remains part of the preserved project history and source materials.

Boofy-Protocol

파일 탐색기

# CDN으로 사용하기

Was this content helpful?

Recent Feedback

Download README