# Blast Deployment Proposal
**URL:** https://community.ver.ax/t/blast-deployment-proposal/49
**Category:** Verax Improvement Proposals
**Created:** [February 15, 2024, 2:03am UTC](https://community.ver.ax/t/blast-deployment-proposal/49 "2024-02-15T02:03:14Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@serp1337](https://community.ver.ax/u/serp1337)
#### Post date: [February 15, 2024, 2:03am UTC](https://community.ver.ax/t/blast-deployment-proposal/49/1 "2024-02-15T02:03:14Z")
# New Chain Deployment Proposal: Deploy Verax on Blast
Author[s]: @0xScore
Title: Deploy Verax on Blast
Type: Cross-Chain Deployment Proposal
* * *
## Proposal Summary
We propose to launch Verax on Blast.
## Overview of the Proposal
Blast has gathered more than $1.5b in TVL even before the mainnet launch, which makes it one of the biggest chains in terms of TVL.
There are a lot of dapps with good potential who can use attestations for such use cases as gaming, yield farming, and many more.
## Motivation
Blast Ecosystem has a lot of Dapps that can implement Verax technology.
Also, it’s very easy to deploy Verax on Blast; however, the impact will be big as it should reduce the cost of identity protocols on Blast.
## Technical considerations
Deployment will happen in the Blast Testnet and then be merged into the Blast mainnet once it’s launched.
There should not be any difficulties, as Blast is L2 and EVM compatible.
### Design Considerations
There are no new design considerations to take into account.
### Deployment Considerations
TheGraph supports blasts.
## Next Steps
The 0xScore team will handle the deployment process if the proposal gets approved.
## References and Links
> **[About Blast - Blast Developer Documentation](https://docs.blast.io/about-blast)**
>
> Blast is the only Ethereum L2 with native yield for ETH and stablecoins.
---
### Author:  [@alain\_ncls](https://community.ver.ax/u/alain_ncls)
#### Post date: [February 15, 2024, 9:24am UTC](https://community.ver.ax/t/blast-deployment-proposal/49/2 "2024-02-15T09:24:59Z")
One quick technical note:
- **Goldsky** doesn’t seem to be indexing Blast: [Supported networks - Goldsky](https://docs.goldsky.com/chains/supported-networks)
- But **TheGraph** is: [Supported Networks | Docs | The Graph](https://thegraph.com/docs/en/developing/supported-networks/)
So we’d need an update on the subgraph config to handle that.
---
### Author:  [@simon.brown](https://community.ver.ax/u/simon.brown)
#### Post date: [February 19, 2024, 5:19pm UTC](https://community.ver.ax/t/blast-deployment-proposal/49/3 "2024-02-19T17:19:21Z")
I just wanted to point out that a multisig contract owner was suggested for @Ollie’s proposal for the Berachain deployment, so I think the same should apply here (and to all deployments really). Is agreeable @serp1337 ?
---
### Author:  [@serp1337](https://community.ver.ax/u/serp1337)
#### Post date: [February 19, 2024, 6:02pm UTC](https://community.ver.ax/t/blast-deployment-proposal/49/4 "2024-02-19T18:02:16Z")
Yeah, I am totally for the multisig contract