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
I like the idea for the EIP7246 standard but I believe it's necessary to bake in a way (within the standard) to transfer encumbrances. So here is my proposed addition:
function transferEncumbranceRights(addressowner, addressnewTaker, uintamount) external {
// Ensure caller has enough encumbrance for the transferrequire(encumbrances[owner][msg.sender] >= amount, "Insufficient encumbrance");
// Reduce the encumbrance of the old taker
encumbrances[owner][msg.sender] -= amount;
// Increase the encumbrance of the new taker
encumbrances[owner][newTaker] += amount;
// Emit an event for trackingemitEncumbranceRightsTransferred(owner, msg.sender, newTaker, amount);
}
event EncumbranceRightsTransferred(
addressindexedowner,
addressindexedoldTaker,
addressindexednewTaker,
uintamount
);
I might be completely off-base here, but wanted to get the discussion started. I am also happy to make a PR.
Another alternative to address this use-case would be to simply require the issuing of receipt tokens whenever an encumbrance is created. But I think that might be too much overhead compared to adding this simple function.
Please let me know your thoughts.
The text was updated successfully, but these errors were encountered:
This is a great point @adrianmcli , mechanically (and in an efficient manner) this should be possible to do in whole or in part and to a single or multiple new takers
This is important for the types of products it would enable on-top
I originally made a comment here regarding this: ethereum/EIPs#7246 (comment)
I like the idea for the EIP7246 standard but I believe it's necessary to bake in a way (within the standard) to transfer encumbrances. So here is my proposed addition:
I might be completely off-base here, but wanted to get the discussion started. I am also happy to make a PR.
Another alternative to address this use-case would be to simply require the issuing of receipt tokens whenever an encumbrance is created. But I think that might be too much overhead compared to adding this simple function.
Please let me know your thoughts.
The text was updated successfully, but these errors were encountered: