You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Announce fee configuration and deposit changes #1189
Only withdraw emits an event (fee_withdrawn, without version topic or admin). init, set_fee and deposit are silent.
Why this matters
Fee-rate changes directly affect revenue splits; without events they cannot be audited or alerted on.
Scope
Emit fee_init, fee_set(old, new) and fee_deposited(caller, amount, total) events with a version topic, and add the admin to fee_withdrawn topics.
Relevant code in CalloraOrg/Callora-Contracts:
contracts/fee/src/lib.rs
Priority
Low
Acceptance criteria
Each state-changing function emits one event
fee_set includes old and new bps
Event topics follow the workspace (name, v1, subject) shape
Deposits of zero or negative amounts emit no event
Validation
cargo test -p callora-fee events
Non-goals
Typo-only, formatting-only, or cosmetic changes.
Unrelated refactors, dependency upgrades, or broad rewrites.
Removing safeguards or weakening validation to make tests pass.
Contributor application
Before coding, describe the affected modules, proposed state/invariant changes, test strategy, compatibility considerations, and an estimate. Wait for assignment before starting implementation.
PR requirements
Use a feature branch and include Closes #<issue-number>. Address every criterion, map criteria to code and tests, explain security and failure-mode handling, and ensure CI passes.
Quality review
A maintainer will assess correctness, completeness, test depth, compatibility, observability, and adverse-case handling. A substantive implementation is required; merge or CI status alone does not guarantee reward eligibility.
@premiuslol has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
I checked the current issue #1189, 'Announce fee configuration and deposit changes'. The affected paths include contracts/fee/src/lib.rs. I would reproduce the failing path, fix the underlying source/setup behavior rather than weaken the assertions, and add focused regression coverage. I would run the relevant repository tests plus lint/typecheck/build checks that apply before submitting. I can complete this once assigned.
Activity
[-]Keep leaderboard rank pages deterministic[/-][+]Add focused test coverage for contracts/rescue/src/lib.rs[/+][-]Add focused test coverage for contracts/rescue/src/lib.rs[/-][+]Announce fee configuration and deposit changes[/+]devgbmuyiwa commentedon Sep 27, 2026
@devgbmuyiwa has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @devgbmuyiwa to this issue.
premiuslol commentedon Sep 30, 2026
@premiuslol has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @premiuslol to this issue.
Ayfataan commentedon Sep 30, 2026
@Ayfataan has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ayfataan to this issue.
Rodrigoue9 commentedon Oct 3, 2026
Hi @maintainers! I'd like to work on this issue. Here is my proposed technical approach:
Proposed Technical Approach:
require_auth), and gas optimization.soroban-sdk::Envverifying both success and failure execution paths.Key Files:
contracts/**/src/lib.rs(contract entrypoints and interface implementations)contracts/**/src/types.rsorstorage.rs(types, data keys, and state)contracts/**/src/test.rs(unit tests and integration vectors)Verification & Testing:
cargo testacross all contract crates verifying 100% pass rate.cargo clippy --all-targets -- -D warningsandcargo fmt --check.soroban contract build.Relevant Track Record:
I have successfully implemented and merged multiple production PRs across the Stellar ecosystem and Web3 open-source projects (e.g., Bitcoindefi/OpenAO #218, cybermax4200/stellar-did-credit #898 & #900, and FindMalek/sonaraem #416).
Please feel free to assign this issue to me so I can proceed with the implementation. Thank you!
shobhamerabacha-star commentedon Oct 7, 2026
Hello maintainers,
I am interested in taking up
Announce fee configuration and deposit changes.Implementation approach:
Could you please assign this issue to me? Looking forward to delivering a clean PR.
Bkizzy16 commentedon Oct 15, 2026
@Bkizzy16 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Bkizzy16 to this issue.
lienhoatienphung-svg commentedon Oct 16, 2026
Hi! I have implemented and verified this in #1377 with full unit test coverage and rustfmt compliance.
feat(fee): emit versioned events for init, set_fee, deposit, and with…
comrade10-coder commentedon Oct 16, 2026
@comrade10-coder has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @comrade10-coder to this issue.
Ezekiel146 commentedon Oct 16, 2026
@Ezekiel146 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ezekiel146 to this issue.
Mrbleatz commentedon Oct 16, 2026
@Mrbleatz has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Mrbleatz to this issue.