Skip to content
This repository has been archived by the owner on Oct 24, 2023. It is now read-only.

Obscuro Go To Market Discussion

Gavin Thomas edited this page Mar 15, 2022 · 1 revision

Key Notes

Arbitrum broad along portfolio customers for their launch Little loyalty in crypto We need to build loyalty Make it difficult for other networks to steal customers = protection What kind of relationships can be create to achieve loyalty And / or achieve a degree of legitimacy a la Ethereum

Where to compete: 1. Privacy 2. Cost: Obscuro could be attractive on cost reasons alone, with privacy as a future need a. Pricing needs to be good enough but does not need to be a differentiator. Usually pricing is a reflection of network congestion. b. What about developer cost? Ego pitched itself as providing privacy easily. 3. EVM

Do we want to be the general purpose L2 regardless of privacy? Probably not because it means privacy gets deprioritised so Obscuro is cheap and scalable

Reality is that privacy solutions are not gaining traction. Could be because: Privacy is not done easily, e.g. Aztec requires dipping in and out of Ethereum more than once Pioneers don't care about privacy, they want people to see what they are doing

Privacy on smart contracts / tokens / NFTs is too new. Monero / Zcoin have been around for 2+ years... Have they gained traction? Who are they competing with? Bitcoin?

Binance Smart Chain encouraged further forks, e.g. PancakeSwap forked UniSwap BSC subsidised PancakeSwap etc via grants from Binance. Brings lots of people to BSC. BSC lost market value because it did not retain market share / remain attractive once the money ran out

Make grants available: not to pay for dev costs (cos its super easy to port over) but rather allow us to pay a yield (e.g. fee from liquidity pool) Grants do not build loyalty

There is a whole new class of use case which we can only guess at.

Commerce should be included as a use case family. Institutionalised use case: private smart contracts would mean private SLAs Also could be an insurance use case: terms of the contract entirely private (payout, terms etc) Could make use of oracles, e.g. Cloud service uptime Could be a hackathon topic. Longer term use case ^^

Reputation of Obscuro is important because would be asking participants to put value into contracts they cannot see because they are encrypted 3rd parties can provide assurance the smart contract code is good / audited successfully The smart contract developer could be reputable

Need to think through how Obscuro can be trusted and** how applications on Obscuro can be trusted** Vital that people can check the code of the contract they are interacting with SGX attestation covers the L2 code but not the actual app / smart contract E.g. Compate the hash of the byte code

Samples required on testnet to demonstrate functions etc

Knowledgebase

Community

Designs and Thinking

Branding

Delivery

Clone this wiki locally