# Add Specs: Composable

**URL:** <https://community.lavanet.xyz/t/add-specs-composable/59>\
**Category:** 🗜️ Specifications\
**Created:** [February 16, 2024, 2:23pm UTC](https://community.lavanet.xyz/t/add-specs-composable/59 "2024-02-16T14:23:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kokos](https://yyz1.discourse-cdn.com/flex007/user_avatar/community.lavanet.xyz/kokos/32/9_2.png) [@Kokos](https://community.lavanet.xyz/u/Kokos)\
**Post date:** [February 16, 2024, 2:23pm UTC](https://community.lavanet.xyz/t/add-specs-composable/59/1 "2024-02-16T14:23:28Z")

</div>

```auto
{
    "proposal": {
        "title": "Add Specs: Composable",
        "description": "Adding new specification support for relaying Composable data on Lava",
        "specs": [
            {
                "index": "CEN1",
                "name": "composable mainnet",
                "enabled": false,
                "imports": [
                    "COSMOSSDK"
                ],
                "reliability_threshold": 268435455,
                "data_reliability_enabled": true,
                "block_distance_for_finalized_data": 0,
                "blocks_in_finalization_proof": 1,
                "average_block_time": 5780,
                "allowed_block_lag_for_qos_sync": 2,
                                "shares" : 1,
                "min_stake_provider": {
                    "denom": "ulava",
                    "amount": "50000000000"
                }
            }
        ]
    }
}

```

Composable is designed to provide a seamless and trust-minimized infrastructure for building and deploying decentralised applications across different ecosystems.

---

<div class="post-metadata">

**Author:** ![kagemnikarimu](https://yyz1.discourse-cdn.com/flex007/user_avatar/community.lavanet.xyz/kagemnikarimu/32/23_2.png) [@kagemnikarimu](https://community.lavanet.xyz/u/kagemnikarimu)\
**Post date:** [February 16, 2024, 2:39pm UTC](https://community.lavanet.xyz/t/add-specs-composable/59/2 "2024-02-16T14:39:20Z")

</div>

Hey @Kokos🙂

Excited to see the first stages of the proposal formation here! 🎉 🔥

I would love just a little bit more information so I could share with some other parties…

Do you mind answering the following questions?

- Where are you in the process of adding the spec? (I.e. what step did you stop on). For reference as to what the steps are see the [spec proposal guide](https://docs.lavanet.xyz/spec-guide).

- Why did you choose to add this spec to Lava? Are you using it for a project? What sorts of behaviors do you want it to support (debug, archive, etc.)?

- What help do you need? Was there anything confusing?

- Can you provide some links to the chain in question for reference?

Any or all of this would be extremely helpful!! 💯

---

<div class="post-metadata">

**Author:** ![Kokos](https://yyz1.discourse-cdn.com/flex007/user_avatar/community.lavanet.xyz/kokos/32/9_2.png) [@Kokos](https://community.lavanet.xyz/u/Kokos)\
**Post date:** [February 16, 2024, 3:03pm UTC](https://community.lavanet.xyz/t/add-specs-composable/59/3 "2024-02-16T15:03:13Z")

</div>

I just started creating the specification, I’m studying the documentation more carefully. I’m looking at examples of other specifications.

Why did you choose Composable? We are active validators in the Composable project. I don’t need help yet, but I think I will soon.  
Here is a description of the project [https://docs.composable.finance/](https://docs.composable.finance/) here is a link to the explorer [NodeStake Explorer](https://explorer.nodestake.org/composable/)  
The project exists in several blockchains. We validate online using cosmos sdk.