Skip to content
This repository has been archived by the owner on Apr 30, 2024. It is now read-only.

Commit

Permalink
update integration test description
Browse files Browse the repository at this point in the history
  • Loading branch information
Raul committed Feb 2, 2024
1 parent 7f37d30 commit e176eab
Showing 1 changed file with 18 additions and 14 deletions.
32 changes: 18 additions & 14 deletions test/foundry/modules/licensing/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,20 +28,20 @@ Alice burns L1, P1 is set in IP2
1) P1 does not allow for derivatives
1.1) Don tries to mint a license from P1 in IP2 -> fails ✅
1.2) Alice tries to mint a license from P1 in IP2 -> fails ✅
1.3) Alice tries to set a policy --> fails?
1.3) Alice tries to set a policy --> fails????

// Edge case, later on, Alice buys the right from her licensor to make derivatives
// Setting the parent again should work in this case, P2 should be
1.4) Bob mints L2 with P2 (allows derivatives) and sends it to Alice 🚧
Alice burns L2 and P2 is set in IP2 🚧
Alice can mint now L3 with P2? 🚧
1.4) Bob mints L2 with P2 (allows derivatives) and sends it to Alice
Alice burns L2 and P2 is set in IP2
Alice can mint now L3 with P2?


1) P1 allows for derivatives of this derivatives, but meaning P1 propagates down, no other can be set (reciprocal == true) 🚧
2.1) Don tries to mint a license from P1 in IP2 -> License mints, has P1 🚧
2.2) Alice tries to mint a license from P1 in IP2 -> License mints, has P1 🚧
1) P1 allows for derivatives of this derivatives, but meaning P1 propagates down, no other can be set (reciprocal == true)
2.1) Don tries to mint a license from P1 in IP2 -> License mints, has P1
2.2) Alice tries to mint a license from P1 in IP2 -> License mints, has P1
2.3) Alice tries to set P2 in IP2 -> Fails, reciprocal means no different policies allowed,
and you cannot add the same policy twice 🚧
and you cannot add the same policy twice

# Commercial
Bob owns IP1
Expand Down Expand Up @@ -107,12 +107,16 @@ P1 - Social Remixing
P2 - Commercial Activity

So we have:
An original work A, has P1 and P2 set
people can remix A into B and B into C, all of with P1
B can buy P2 from A.
C can't buy P2 from A?
C can't buy P2 from B?
Once B has bought P2, C can buy P2 from B?
- An original work A, has P1 and P2 set
- People can remix A into B and B into C, all of with P1
- P2 is permissionless (since it's set on A)
- B can buy License from A with P2 and link if it passes verifications
- C can buy License from A with P2 and link if it passes verification

- P2 is NOT permissionless (commercializers are set ) // TODO: commercializer, whitelist or token gating
- B can buy License from A with P2 and link if CommercializerHelper agrees
- C can buy License from A with P2 and link if CommercializerHelper agrees



# DISPUTED CASES
Expand Down

0 comments on commit e176eab

Please sign in to comment.