---
# System prepended metadata

title: VSC Launches it's first HIVE multisig

---



We are happy to announce the successful launch of VSC's first HIVE multisig! 

### Important headlines

- Multisig operational for the testnet
- First successful on chain interaction from smart contract


![](https://hackmd.io/_uploads/B1fyUEq53.png)


Above is a list of the multisig benefactors on the @vsc.ptk-d12e6110 hive account. Currently 7 nodes have the multisig enabled for a 4/7 consensus. As more nodes join the multisig adjustments will occur to always require atleast 51% approval. Note: the @vaultec account is also part of the multisig as an emergency backup during the development process. If the nodes become corrupt for whatever reason the account can be recycled for testnet use. 


First successful smart contract operation through the multisig! 

![](https://hackmd.io/_uploads/SJB-IE99h.png)



### Acknowledgements

We acknowledge that multisigs are not the final solution to perfect L2 security or security in general. With multisigs there must be an adequate number of nodes to safely operate the multisig securely, proper consensus structure ensuring bad actors cannot reach majority consensus and many other unforseen issues outside the scope of this article. We actively are doing work to ensure VSC's multisig is as safe as possible and not use multisigs where possible.

However, for the forseeable future the only way VSC can interact with HIVE is via a multisig. If ever basic L1 smart contracts become a reality we can move more functionality onto the chain and reduce possible risk vectors. For now, security measures can be implemented to make the multisig secure beyond reasonable doubt via consensus. 