baseline VS opium-protocol-v2

Ethereum is by far the most widely adopted blockchain by enterprises. Ethereum’s Enterprise Ethereum Alliance (EEA) is the largest blockchain-enterprise partnership program and Ethereum is by far the most frequently leveraged blockchain for proof of concepts and innovation in the blockchain space by enterprises. Meanwhile, there are protocols like the Baseline protocol which is a shared framework which allows enterprises to use Ethereum as a common frame of reference and a base settlement layer without having to give up privacy when settling on the public Ethereum mainnet. This framework makes adopting Ethereum much easier for other enterprises. Another example is EY’s “Nightfall”, a Zero Knowledge optimistic rollup which provides full privacy and cheaper transactions for enterprise use.

Have a look at decentralised finance (DeFi), have a look at at https://docs.baseline-protocol.org/ , Read about NFTs a little more, read about what a DAO is and think about why crypto may be interesting because of that.

The Baseline Protocol is a new standard that is going to be adopted by enterprises globally. It is a standard created by folks from Enterprise Ethereum Alliance, and led by a team of professionals from several institutions like EY, Microsoft, Consensys, Unibright, SAP, and so on, in different capacities. The protocol is meant to synchronize data between 2 entities while keeping data private + secure. https://docs.baseline-protocol.org/

The Baseline protocol by EY, Microsoft, etc was created specifically for this purpose. It allows SAP and other software to sync up across organizations without using proprietary code and also allows for verified business logic to run that everyone on the system can trust. Coca-Cola is using it to get a real time view of their supply chains, Microsoft is using it for their Xbox licenses, lots of federated industries are using it as a common frame of reference for prices, purchase orders, and other data that multiple organizations share and need to all rely on.

May I introduce you to the baseline protocol: https://docs.baseline-protocol.org/

I don't know the Baseline project, the repo looks active, but the last release (0.1.0) is from 1 year https://github.com/eea-oasis/baseline Mostly developed by 2-3 dev and 1 this year

Ethereum is by far the most widely adopted blockchain by enterprises. Ethereum’s Enterprise Ethereum Alliance (EEA) is the largest blockchain-enterprise partnership program and Ethereum is by far the most frequently leveraged blockchain for proof of concepts and innovation in the blockchain space by enterprises. Meanwhile, there are protocols like the Baseline protocol which is a shared framework which allows enterprises to use Ethereum as a common frame of reference and a base settlement layer without having to give up privacy when settling on the public Ethereum mainnet. This framework makes adopting Ethereum much easier for other enterprises.

Maybe this is just my very biased view (okay, you are also asking this in a Ethereum subreddit), but the discussion which blockchain is suitable for which use-case slowly gets replaced by the question, which scaling solution and which off-chain design patterns are the most suitable for your application. And the blockchain will be Ethereum, an enterprise variant of it (see Quorum) or at least compatible with it (see Baseline Protocol). So for me the comparison of different blockchain types, their throughput, etc. is not very interesting as it is generally very hard to objectively compare those different approaches and I'm sure that many blockchains were built with very different use-cases in mind (see IOTA or VeChain).

The struct above is the schema that we use in the Opium Protocol. Let’s quickly walk through it: uint256 margin: aka the reference collateral that is (usually) parsed by the IDerivativeLogic SyntheticId getMargin function to set the collateral requirements of the option contract. uint256 endTime: aka the maturity date of the contract. It is the point in time at which the buyers will have the right to exercise their contract. uint256[] params: option contracts can differ greatly in the complexity of their financial requirements, as such Opium uses a dynamic array to ensure a high degree of flexibility to the consumers of the protocol, as to enable them to encode arbitrary parameters in their LibDerivative asset definition if needed. One convention to keep in mind is that, however, the first item of the params array is always expected to be the strike price. The strike price is the value that determines the profitability of an option upon expiry: if the market price is above the strike price in case of a call option or the market price is below the strike price in the context of a put option, the option is said to be ‘in the money’ and the buyer stands to make a profit. Vice-versa, the option is said to be out of the money and the buyer stands to lose the premium or the collateral that they had to exchange for the ownership of the option contract. oracleId: oracles are the entities that inform the Opium Protocol about the value of an asset upon its maturity date. The Opium Protocol does not enforce any specification as for what can be used as an oracle, be it on-chain or off-chain. token: the address of the ERC20 token to be used as a collateral syntheticId: the address of the contract where the financial logic of the derivative is encoded. The Opium Protocol expects the syntheticId contracts to be compliant with the specifications of the IDerivativeLogic interface.