{"componentChunkName":"component---src-pages-sccp-sccp-markdown-remark-frontmatter-sccp-tsx","path":"/sccp/sccp-217/","result":{"data":{"markdownRemark":{"fileAbsolutePath":"/vercel/path0/content/sccp/sccp-217.md","frontmatter":{"sip":null,"sccp":217,"title":"Lower Atomic Twap Window","network":"Ethereum","author":"Kaleb (@kaleb-keny)","type":"Governance","proposal":"https://snapshot.org/#/snxgov.eth/proposal/bafkreifjfpqag7spyytkzrjeliik43ze4lxicvecty2yypizfmn27g3eju","implementor":null,"release":null,"created":"2022-07-18T00:00:00.000Z","updated":null,"status":"Implemented"},"html":"

Simple Summary

\n

This sccp proposes to lower atomicTwapWindow to 60 seconds.

\n

Abstract

\n

The atomicTwapWindow is the twap window used when fetching the uniswap price.

\n

Motivation

\n

Lowering the atomicTwapWindow reduces the twap impact on the traders price as it converges towards the spot exchange. This is necessary until SIP-258 is implemented.\nIt is worth noting that Twap protection is not needed to protect against flash attacks, given that the uniswap price used is that set at the begining of the block. Furthermore, chainlink protection limits the amount of upside exploiters can earn by moving the uniswap-v3 pool price for several consecutive blocks and makes such an attack unprofitable due to the cost of moving the univ3 pools.

\n

Copyright

\n

Copyright and related rights waived via CC0.

"}},"pageContext":{"id":"74ea31dc-1bac-5b1a-a002-18e34568037a","frontmatter__sccp":217,"__params":{"frontmatter__sccp":"217"}}},"staticQueryHashes":[]}