@croptop/core-v6 0.0.52 → 0.0.53
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +2 -5
- package/CHANGELOG.md +0 -64
package/package.json
CHANGED
|
@@ -1,19 +1,16 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@croptop/core-v6",
|
|
3
|
-
"version": "0.0.
|
|
3
|
+
"version": "0.0.53",
|
|
4
4
|
"license": "MIT",
|
|
5
5
|
"repository": {
|
|
6
6
|
"type": "git",
|
|
7
7
|
"url": "git+https://github.com/mejango/croptop-core-v6"
|
|
8
8
|
},
|
|
9
9
|
"files": [
|
|
10
|
-
"CHANGELOG.md",
|
|
11
10
|
"foundry.toml",
|
|
12
11
|
"references/",
|
|
13
12
|
"remappings.txt",
|
|
14
|
-
"script/
|
|
15
|
-
"script/Deploy.s.sol",
|
|
16
|
-
"script/helpers/",
|
|
13
|
+
"script/",
|
|
17
14
|
"src/"
|
|
18
15
|
],
|
|
19
16
|
"engines": {
|
package/CHANGELOG.md
DELETED
|
@@ -1,64 +0,0 @@
|
|
|
1
|
-
# Changelog
|
|
2
|
-
|
|
3
|
-
## Scope
|
|
4
|
-
|
|
5
|
-
This file describes the verified change from `croptop-core-v5` to the current `croptop-core-v6` repo.
|
|
6
|
-
|
|
7
|
-
## Current v6 surface
|
|
8
|
-
|
|
9
|
-
- `CTDeployer`
|
|
10
|
-
- `CTProjectOwner`
|
|
11
|
-
- `CTPublisher`
|
|
12
|
-
- `CTAllowedPost`
|
|
13
|
-
- `CTDeployerAllowedPost`
|
|
14
|
-
- `CTPost`
|
|
15
|
-
|
|
16
|
-
## 0.0.47 — Bump v6 deps to nana-core-v6 0.0.53 cohort
|
|
17
|
-
|
|
18
|
-
- `@bananapus/core-v6`: `^0.0.49 → ^0.0.53` ([PR #145](https://github.com/Bananapus/nana-core-v6/pull/145)).
|
|
19
|
-
- `@bananapus/721-hook-v6`: `^0.0.49 → ^0.0.50`.
|
|
20
|
-
- `@bananapus/suckers-v6`: `^0.0.43 → ^0.0.46`.
|
|
21
|
-
- All `JBRulesetMetadata` test literals patched to include `pauseCrossProjectFeeFreeInflows: false`.
|
|
22
|
-
|
|
23
|
-
## Summary
|
|
24
|
-
|
|
25
|
-
- `CTPost` and the related allowlist structs now carry split-routing data, so a post can route part of its payment through `JBSplit[]` recipients.
|
|
26
|
-
- The deployer now acts as the data-hook entry point instead of wiring the 721 hook directly, which is what enables the intended omnichain and sucker-aware cash-out behavior.
|
|
27
|
-
- v6 closes several correctness gaps that were easy to miss in v5: duplicate posts in a batch are rejected, existing tiers use on-chain pricing instead of caller-supplied pricing, and stale tier mappings are recreated when tiers were removed externally.
|
|
28
|
-
- The repo was moved to the v6 dependency set and Solidity `0.8.28`.
|
|
29
|
-
|
|
30
|
-
## Verified deltas
|
|
31
|
-
|
|
32
|
-
- `CTPost` gained `splitPercent` and `JBSplit[] splits`.
|
|
33
|
-
- `CTAllowedPost` and `CTDeployerAllowedPost` gained `maximumSplitPercent`.
|
|
34
|
-
- `ICTPublisher.allowanceFor(...)` now returns five values instead of four because `maximumSplitPercent` is part of the result.
|
|
35
|
-
- `CTDeployer` now points project metadata to itself as the data hook instead of pointing directly at the 721 hook.
|
|
36
|
-
- The repo carries dedicated regression tests for duplicate-URI fee evasion, stale tier mappings, and existing-tier pricing.
|
|
37
|
-
|
|
38
|
-
## Breaking ABI changes
|
|
39
|
-
|
|
40
|
-
- `CTPost` is not v5-compatible because it now includes `splitPercent` and `splits`.
|
|
41
|
-
- `CTAllowedPost` and `CTDeployerAllowedPost` are not v5-compatible because they now include `maximumSplitPercent`.
|
|
42
|
-
- `ICTPublisher.allowanceFor(...)` return decoding changed because of the added field.
|
|
43
|
-
|
|
44
|
-
## Indexer impact
|
|
45
|
-
|
|
46
|
-
- Any event or log decoding path that embeds `CTPost` or `CTAllowedPost` must be updated for the new struct layouts.
|
|
47
|
-
- Post-publishing integrations should not assume the old "all payment goes to treasury" model once split-bearing posts are live.
|
|
48
|
-
|
|
49
|
-
## Migration notes
|
|
50
|
-
|
|
51
|
-
- Rebuild any ABI or indexer code that decodes `CTPost` or `CTAllowedPost`. Their layouts are not v5-compatible.
|
|
52
|
-
- If you integrated the deployer as if the 721 hook were the direct data hook, update that assumption. The deployer is now part of the routing path.
|
|
53
|
-
- Re-check any fee logic that trusted caller-supplied prices for existing tiers. That is not the v6 behavior.
|
|
54
|
-
|
|
55
|
-
## ABI appendix
|
|
56
|
-
|
|
57
|
-
- Changed structs
|
|
58
|
-
- `CTPost`
|
|
59
|
-
- `CTAllowedPost`
|
|
60
|
-
- `CTDeployerAllowedPost`
|
|
61
|
-
- Changed decoding expectations
|
|
62
|
-
- `ICTPublisher.allowanceFor(...)`
|
|
63
|
-
- Behaviorally important surface shift
|
|
64
|
-
- deployer acts as the data-hook entrypoint
|