Rootul P

Metric to track state growth

1

## Context Based on recent discussions, it seems important to track state growth over time. I propose we add a metric + dashboard to monitor state growth over time. ##...

Consider removing extraneous fields in `MsgPayForBlobs`

1

## Context Motivated by a Slack conversation. cc @cmwaters The `MsgPayForBlobs` type appears to contain two extraneous fields: `namespaces` and `share_versions`. ```proto // MsgPayForBlobs pays for the inclusion of a...

Create parameter for base fee per PFB

1

## Context During the "Default Params Presentation" presentation at the Paris onsite, we discussed adding a base fee to PFDs so that one PFD with a 100 byte message costs...

Consider making the gas cost constant for PFB signature verification, tx size, read access to accounts

2

## Context > The "fixed cost" is an approximation of the gas consumed by operations outside the function GasToConsume (for example, signature verification, tx size, read access to accounts), which...

Consider script(s) to run node on testnet

2

## Context Contributors to this repo sometimes need to build and run a celestia-app node with their changes on an existing testnet. In this scenario, a contributor usually has to...

Is `DefaultMaxBytes` high enough?

2

## Context https://github.com/celestiaorg/celestia-app/blob/3e6d22cfde678efac4f7c078228e9f294a7a9b8d/pkg/appconsts/initial_consts.go#L12-L14 ## Problem DefaultMaxBytes is used as a consensus param for `MaxBytes` [here](https://github.com/celestiaorg/celestia-app/blob/3e6d22cfde678efac4f7c078228e9f294a7a9b8d/app/default_overrides.go#L156). However, the current `DefaultMaxBytes` doesn't account for the size of the header, the validator set,...

## Context https://github.com/osmosis-labs/osmosis/blob/94e0042d6cbd91ffab05cc71ab214a55e441f89f/x/mint/README.md?plain=1#L26-L36 ## Problem The x/mint README claims that epochs are a week and periods are 3 years but https://medium.com/osmosis/osmo-token-distribution-ae27ea2bb4db claims daily epochs and yearly thirdenings. ## Proposal 1....

https://github.com/awslabs/amazon-managed-blockchain-client-templates/blob/191374e7a01d0033c67b3c8f946a39640a034c2f/templates/fabric-ec2-client.template.yaml#L231 For 1.4.x+ networks, we should use: ``` FABRIC_LOGGING_SPEC=info ``` See: [public docs](https://docs.aws.amazon.com/managed-blockchain/latest/hyperledger-fabric-dev/get-started-create-client.html#get-started-client-configure-peer-cli)

## Context Thanks for this awesome project! I'm successfully using goreleaser-cross to build binaries for multiple platforms with CGO support. Tangent: our project needs this because it uses hardware wallets...

Migrate specs to individual repos

4

## Context - https://github.com/celestiaorg/celestia-app/issues/650 ## Candidates Repos It may aid discoverability if these specs are migrated to a consistent location across repos (i.e. `specs/`) - https://github.com/celestiaorg/celestia-core - https://github.com/celestiaorg/celestia-app - https://github.com/celestiaorg/celestia-node...