feat: call for contributors by introducing Ownership Wrapper

[0xneves]

This card aims to find who is interested in pushing forward the development of Swaplace v2.

The architecture will be very different and security regarding allowances should be checked above all matters.

The core idea of Swaplace v2 is to sell tokenized executions on the blockchain.

You could sell ownership, stake, airdrop, claim functions and delegate to the buyer of said functions.

Please show interest by commenting on this card.

[0xneves]

I'm thinking about using an Ownership Wrapper, where one can delegate ownership to a contract while owning it and then transfer its ownership just like an NFT.

We could build a contract that can mint NFTs and those nfts are ownership over a single contract, and it can be transferred like erc721.

[blackbeard002]

Hey @0xneves I'm interested and excited in pushing forward the development of Swaplace v2 :)

[0xneves]

Hey @0xneves I'm interested and excited in pushing forward the development of Swaplace v2 :)

Awesome!!

We are still in the early stages since the solution will be an independent tech, that will extend the usage of Swaplace without changing the source code. Although this is postponed in the roadmap, there is no reason why we can't move in parallel. Could you contact me on Discord(#0xneves) so I can introduce you to the context? If you enjoy the ride you can end up leading a team ;)

[blackbeard002]

I'm already enjoying the ride of contributing tbh😁. I've pinged and sent a request on discord 😃

[web3-engineer]

Let's build it @0xneves ,I would love to make part of this journey

[0xneves]

I'm changing the name as the Swaplace v2 won't suit this edge case. It's a concept, but we aim to modify a smart contract account (SCA) into a trustless tradable version.

Smart contract account advantages:

• Can own property, such as ownership over other contracts or even soulbond tokens.

Smart contract account issue:

• When you have a SCA, you can hold ownership and tokens. But when you want to trade the ownership of the SCA, there are no guarantees for the new buyer that you won't empty the account by watching the mempool once the trade happens.
• The SCA won't register correctly all the batches it executed in the past and store correctly the ownerships of that SCA.

We aim to build the Ownership Wrapper. Why? Because we want Swaplace to be able to swap anything! We see a future where account abstraction will take over the ownership of the market, allowing people to swap ownership, hence the ownership becomes an ERC721. Since SCAs can execute anything on-chain. We are wrapping up all the history executions of accounts and swapping them as a normal ERC721.

The main problems we are fixing are the ones quoted above, reinforcing:

• We must ensure that the contract activities are locked so the current owner cannot modify the SCA state during the trade (this can be resolved by generating dynamic token IDs based on the current state of the contract). This means you should not be able to retrieve 1 ETH while your SCA is being traded on Swaplace.
• We need to easily be able to tell what are the ownerships that SCA owns from a high-level perspective. This means every single asset (if the asset matters, it will have an interface) should be identified. There are plenty of ways to do this, one way could be using encodeWithSelector to prove that the function would return address(this) as the owner, for instance when calling onlyOwner to the targeted address.

This is all very raw and there is nothing written on it.
This is not our priority right now.
We intend to turn this into an EIP in the future.