Show HN: Slice – Decentralized payments infrastructure based on fractional NFTs
slice.so
slice.so
1. What is the recipient of a slice for payments? Is it a wallet crypto address/ENS domain? Or is it a function in a larger smart contract? It seems this would dictate whether the sender can treat it like a normal ETH/token send or whether they have to use a dApp to send payments. Curious whether senders of payments are locked into your infrastructure or not.
2. What is the process of slice creation? Does one party decide which other parties get a piece of a slice initially, or just own 100% initially?
Somewhat related, I am building infrastructure tools for smart contracts (https://www.blocktimize.io/), and I'm looking for Beta testers who are launching smart contracts -- is there an email I could reach you at?
- The recipient for payments is the slicer, which is a smart contract. If you go onto the slicers page you can copy its address, and yes you can send it ETH however you prefer - not just through the website! (In fact, the payment on the platform is actually a standard ETH transfer). Currently it won't be able to accept other tokens, but I plan to add support eventually in a future release.
- The creation of a slicer involves the mint of ERC1155 tokens, the creation of the slicer smart contract, and establishes the link between the contract and the tokens (so that when a token transfer happens it is also reflected in the slicer logic).
I'm sure most of this aspects will get clear as I publish the contract source code, which I plan to deploy on GitHub soon (btw I'm also looking for devs who may be interested in contributing)
Feel free to reach out on twitter @slice__so, or via email hey@slice.so!