Skip to content

resolve #579 #580 #581 #582: init event, creator fee tests, sell even… - #687

Merged
Chucks1093 merged 1 commit into
accesslayerorg:mainfrom
Johnsmichael150:main
Jul 29, 2026
Merged

Chucks1093 merged 1 commit into
accesslayerorg:mainfrom
Johnsmichael150:main

Conversation

@Johnsmichael150

Copy link
Copy Markdown
Contributor

Brief closing comments:

Close #579

Closing as completed. Initialization now emits a single structured event with the required fields, and tests verify it is emitted only on the first successful initialization.

Close #580

Closing as completed. Creator fee computation is now covered by unit tests for multiple BPS values, flooring behavior, and the zero-fee case.

Close #581

Closing as completed. Integration tests now verify the sell event is emitted exactly once with the correct seller, creator, quantity, proceeds, and ledger values.

Close #582

Closing as completed. Protocol fee BPS reads are centralized in a shared helper, inline storage reads have been removed, and unit tests cover both initialized and uninitialized contract states.

…sslayerorg#582: init event, creator fee tests, sell event fields, protocol fee bps helper

accesslayerorg#579: emit ContractInitializedEvent on first set_fee_config call with admin,
protocol_fee_bps, protocol_fee_recipient, and initialized_at_ledger fields;
add contract_initialization_event.rs integration tests

accesslayerorg#580: add unit tests for creator fee bps computation — 500 bps on 1000 → 50,
250 bps on 1000 → 25, 100 bps on 999 floors to 9, 0 bps always returns 0

accesslayerorg#581: expand KeysSoldEvent with seller, creator_id, quantity, proceeds, ledger;
update sell_key emission to populate new fields; add sell_event_fields.rs
integration test asserting all five fields including proceeds formula match;
update tests/events.rs to use new struct shape

accesslayerorg#582: read_protocol_fee_bps helper and unit tests already present; no changes
@Chucks1093
Chucks1093 merged commit a4c9e0c into accesslayerorg:main Jul 29, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants