Octo-Protocol-org/Octo-Protocol
Octo lets a fintech manage stablecoin deposits on Stellar from a single master wallet: generate a dedicated deposit address per customer, detect deposits in real time, and initiate withdrawals, all behind a REST API with signed webhooks, and a non-custodial key model.
Is Octo-Protocol-org/Octo-Protocol beginner-friendly?
We have not seen enough recent pull requests from outside contributors to Octo-Protocol-org/Octo-Protocol to say how often they are merged. 4 beginner-friendly issues are open now.
- Stars
- 0
- Forks
- 91
- Open beginner issues
- 4
- Indexed issues
- 219
- Avg merge
- 5h 23m
- Merged PRs (30d)
- 4
- Dominant language
- Rust
- License
- MIT
- Last GitHub push
- Oct 18, 2026
- Latest indexed
- Oct 19, 2026
- Contributing guide
- Contributing guide
- Code of conduct
- No code of conduct
- Beginner labels
- good first issue help wanted
How to contribute to Octo-Protocol-org/Octo-Protocol
- Read the contributing guide first: it says how the maintainers want changes proposed, tested and reviewed.
- It ships a Dockerfile or Docker Compose file, so you can run it without installing its whole toolchain.
- Your contributions will be published under the project's MIT license.
- Pick one of the 4 open beginner-friendly issues below and comment that you want to work on it before you start.
Issues somebody may already be working on are listed last. List everything by date
-
area/integration area/testing enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area/integration area/testing enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area/integration area/testing enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area/integration area/testing enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area/integration area/testing enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Octo-Protocol-org/Octo-Protocol#701 · 1 comment ·
-
area/integration area/testing enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area/integration area/testing enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area/integration area/testing enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
test(evm-core): Verify derivation behaves safely at the highest valid and first invalid child indexOpenarea/contract area/testing enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
-
area/contract area/testing enhancement good first issue help wanted
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Octo-Protocol-org/Octo-Protocol#696 · 1 comment ·
-
area/contract area/testing enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area/contract area/testing enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
area/contract area/testing enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
test(evm-rpc): Table-test Retry-After parsing for seconds, HTTP-date, garbage and negative valuesOpenarea/contract area/testing enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area/contract enhancement good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
docs(evm-core): Add a compiled rustdoc example that derives the first EVM address from a test seedOpenarea/contract documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area/backend area/testing enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
area/backend enhancement good first issue help wanted
Difficulty 3/5 1-2 days Newbie friendliness 78/100
-
area/backend enhancement good first issue help wanted
Difficulty 1/5 Under an hour Newbie friendliness 94/100
-
area/backend area/testing enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area/backend area/testing enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
area/backend area/testing enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
area/backend area/testing enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
area/backend area/testing enhancement good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
area/backend area/testing enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
area/backend documentation good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
area/integration documentation good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
-
area/backend enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area/backend bug good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area/integration bug good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area/backend bug good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area/integration bug good first issue help wanted
Difficulty 3/5 1-2 days Newbie friendliness 72/100
-
area/integration documentation good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
fix(server): Reject a malformed SHUTDOWN_DRAIN_TIMEOUT_SECS instead of silently using 25 secondsOpenarea/backend bug good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area/backend bug good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
fix(resilience): Validate HORIZON_* tuning variables instead of silently defaulting on bad inputOpenarea/backend bug good first issue help wanted
Difficulty 4/5 3-5 days Newbie friendliness 56/100
-
area/integration documentation good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
area/integration documentation good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
-
area/integration documentation good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
area/contract documentation good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
-
area/contract documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
area/backend documentation good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
-
area/backend documentation good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 87/100
-
area/backend documentation good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
area/contract bug good first issue help wanted
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
area/contract bug good first issue help wanted
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
area/contract bug good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
fix(evm-core): Return an error instead of panicking when the signature recovery id is out of rangeOpenarea/contract bug good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area/contract bug good first issue help wanted
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
area/integration bug good first issue help wanted
Difficulty 3/5 1-2 days Newbie friendliness 78/100
Showing the newest 100
This page lists what was indexed most recently. Advanced filter has the whole inventory, narrowed by language, difficulty and how long a task takes.