sunriselayer / gitbook

cover	coverY
.gitbook/assets/Sunrise Cover.png	0

Sunrise

Our documentation is under construction and is being updated regularly, please check back for updates.

Sunrise is a specialized Data Availability (DA) Layer for Fee Abstraction and Proof of Liquidity, supporting the modular paradigm by allowing developers to build rollups/apps with enhanced security and liquidity.

Sunrise extend's Berachain's Proof of Liquidity (PoL) model to rollups and L2s, while retaining compabitility with Celestia architecture. A modular cross-chain yield hub (Gluon) is deployed as a Sovereign Rollup (L2) onto the Sunrise L1 blockchain. This yield hub and Sunrise communicate directly to enable the provision of liquidity (replication of PoL) in exchange for blobspace, allowing for a scaling solution with less net-value extract than pre-existing AltDA providers. PoL on Sunrise mutually increases security and liquidity for both the rollup and Sunrise, a parrallel flywheel effect to PoL as seen on Berachain.

Compatibility with Celestia architecture minimizes onboarding difficulty for rollups. This also means that Sunrise is natively IBC compatible. Rollup-as-a-Service (RaaS) providers who integrated Celestia can integrate Sunrise easily, and Rollup SDKs (e.g. OP stack, Polygon CDK, Rollkit, Sovereign SDK, etc.) that support Celestia, will automatically be compatible with Sunrise.

Sunrise Functions

Celestia-compatible functions:

• Blob Tx
• BlobStream

Sunrise unique functions:

• Proof of Liquidity (PoL)
• DA Fee Abstraction
• Off Chain Blob Data Availability (Sunrise DA v2)
• Sovereign Proof of Liquidity by Gluon

Proof of Liquidity x Data Availability

As mentioned above, Sunrise utilizes Proof of Liquidity to enhance the security of the Sunrise L1, and the liquidity and sovereignty of L2s on Sunrise.

Sunrise also has a mechanism to incentivize DA network whereas other DA networks depend on altruism or voluntary contributions, hence Sunrise can enhance the throughput of the DA network. This feature and the incentive for optional long term data availability enables developers to build not only scalable L2s but also fully on-chain new technologies like AI, Gaming, and so on.

Revenue (Fee Structure)

The protocol generates revenue through three distinct streams.

• Transaction fees
• Swap fees in the liquidity pool
• MEV captured with Skip Protocol

Why should developers use Sunrise?

• Users can utilize DA by liquidity providing without the need for a fee.
• While numerous DEXs already exist, they offer limited differentiation for token issuers. L2 developers will always need to provide liquidity despite Sunrise's existence. However, by providing liquidity to Sunrise's DEX, token issuers gain access to additional utilities through Sunrise's DA, incentivizing them to choose Sunrise over other DA Layers and DEXs that lack comparable benefits.

Integration Stages

Sunrise v1: DAWN

• x/blob module
• x/blobstream module
• x/tokenconverter module
• x/liquiditypool module
• x/liquidityincentive module
• x/swap module
• x/fee module

Sunrise v2: Security and Incentive

• Off Chain Blob Data Availability (Sunrise DA v2)
• Sovereign Proof of Liquidity by Gluon

gitbook's Issues

Joining mainnet page

This page in our Gitbook:

https://ununifi.gitbook.io/docs/nodes-and-validators/validate-mainnet

Requirement:

For Joining mainnet page:

• What is needed
• How to set the requirement
• What is close process
• What is the meaning of the important parameters in app.toml and config.toml
• What files are needed to backup

File to be edited:

https://github.com/UnUniFi/gitbook/blob/main/validators/validate-mainnet.md

References: https://docs.junonetwork.io/validators/joining-mainnet
https://docs.junonetwork.io/validators/mainnet

Integrate UnUniFi's specific module spec documentation to Gitbook

• Establish the pages for the specific module explanations like our chain repository's spec folder contents

The construction image is something like this:
-- Developer
--- nftmarket
-- nftmint
...

Each page must contain the information about the purpose of the module, msg and query, the way to work, specific term explanaiton, etc...

Fill out the explanation of each testnet we have

I added a blank page for the general description of all testnets we have in this PR #29.

Please fill out the TODO content if you're familiar with all testnets' role.
@Senna46 @mkXultra

Setting up Cosmovisor page

This page in our Gitbook:

https://ununifi.gitbook.io/docs/nodes-and-validators/setting-cosmovisor

Requirement:

• How to install cosmovisor
• How to set the proper environment to use
• How to start cosmovisor

File to be edited: https://github.com/UnUniFi/gitbook/blob/main/validators/setting-cosmovisor.md

Reference:
https://docs.junonetwork.io/validators/setting-up-cosmovisor

ununifid Installation and Setup page

This page in our Gitbook:

https://ununifi.gitbook.io/docs/nodes-and-validators/ununifid-installation-and-setup

Requirement:

• How to install ununifid
• What are pre-requisites for it

File to be edited: https://github.com/UnUniFi/gitbook/blob/main/validators/ununifid-installation-and-setup.md

Reference: https://docs.junonetwork.io/validators/getting-setup

feat/contributing-doc

Prepare CONTRIBUTING.md to avoid immature Pull Request.

Set markdown lint config

We need to set the config about lint for markdown files for better cooperation with community members.

Doc of client-ts for developers

The documentation about the way to use cosmos-client-ts for developers is requeired to be set.

I think we can just provide the abundant sample codes and the way to handle (manage) cosmos-client-ts library even now.

The structure would be like this in my mind:
-- client-ts
-- general explanation
-- cosmos-client-ts
-- ununifi-client-ts
...

UnUniFi Error and Bugs Found

1)Your Twitter pages invitation link in discord already expired

2)Unable to claim faucet using metamask "Error Message show Failed: Http failure response for https://c.private-test.ununifi.cauchye.net:8001: 0 Unknown Error"

3)Do not have an automatic switch network in metamask

4)Connect Wallet Status "Remark disconnect wallet if your wallet already connected in ununifi dashboard"

5)Vote Proposals "You can vote already expired proposals error show "
An error has occur: Error: failed to execute message; message index: 0: 3: an inactive proposal"
Disable voting if proposals already ended

wallet use for testnet
ununifi1kac8reet5660tkw5ryx45asf6f26ujuf7272fp