AE

Mef1994

 MOON INCOMING

Mef1994

 BIG PUMP INCOMING 🚀🚀 $HEGE

goldyluckinblokchain


Mef1994

 HUGE PUMP INCOMING 🚀🚀 $HEGE

Brown_Noiser

Although that word has been used by leftist media a lot lately to bash Republican candidates, I'll admit Musk has always been a little weird. X is a stupid name for a social media platform IMO. And he named one kid X AE12 or something weird af. But he's pretty goddamn smart and has done a lot to advance humanity too.

Mef1994

 HUGE PUMP SOON $HEGE 🚀🚀

Mef1994

 $HEGE SOON 🚀🚀

Mef1994

 BEST TIME to BUY BEFORE huge pump 🚀🚀 $HEGE

Mef1994

 HUGE PUMP INCOMING !! $HEGE TOP MEMECOIN WITH TOP QUALITY CONTENT 🚀🚀

Mef1994

Wow nice 🚀 best time to buy before huge pump 

Mef1994

 MOON INCOMING 🚀🚀

kehe3006

$HEGE ready for take off! Cant wait till we reach new ATH very soon! 200% upwards potential short term! E 

kehe3006

$HEGE is the most undervalued meme coin right now! I accumulate everyday because the breakout is imminent! 

Mef1994

 MOON INCOMING 🚀🚀

Mef1994

 MOON INCOMING 🚀🚀 $HEGE TOP ON SOL

goldyluckinblokchain

Shots fired! 

Mef1994

 MOON SOON $HEGE 🚀🚀

Mef1994

 NOW IS BEST TIME TO BUY BEFORE HUGE PUUUMP 🚀🚀 $HEGE

Enschede2

Interestingly this post would be the opposite of the following: https://www.binance.com/en-AE/square/post/11489306715377 It would be very weird for them to remove something fron the securities list, and then put it back on a few days later, either way I'm pressing "X" considering the source of OP's article, I'm guessing there's more nuance to it

CointestMod

#Polygon Con-Arguments Below is a Polygon con-argument written by a deleted user. > ####**Has plenty of competitors, including itself** > > Currently, Polygon PoS is competing against optimistic L2 blockchains like Arbitrum One and Optimism. Arbitrum has nearly [2x the TVL as Polygon](https://defillama.com/chains), and Optimism has almost caught up. > > Polygon's future zkEVM rollup is also competing against other zkEVM rollups. Once its zkEVM is released, it's possible it's going to split the Polygon community between those who want to stay on the sidechain and those who want to use the zkEVM. **If you look at their [zkEVM testnet](https://explorer.public.zkevm-test.net/txs?block_number=143530&index=0&page_number=1&page_size=50&pages_limit=200), fees are paid in Ether, not MATIC.** That's bearish for MATIC token utility. > > **TVL has dropped considerably compared to L2s** > > One year ago back in Jan 2022, [Polygon TVL was $4.8B USD](https://defillama.com/chain/Polygon) while the combined [Layer 2 rollup TVL was $5.4B USD](https://l2beat.com/scaling/tvl). While L2 TVL has increased a little despite the bear market, Polygon's TVL has collapsed by 75% to $1.2B. > > **Growing dApp competition from L2 rollups** > > A year ago, Polygon PoS was unique in that it was the only network besides Ethereum that had OpenSea support. Now OpenSea supports a dozen different networks, including competing Layer 2 rollups networks like Optimism, Arbitrum One, and even Arbitrum Nova. So there's a lot more competition. > > **Declining social media support** > > With L2 rollups developing so quickly, many in the Ethereum community have turned against Polygon, creating a narrative that it's "just a sidechain", not a true Layer 2. > > The 0xPolygon subreddit has become more of a ghost town with noticeable amounts of spam posts. I don't think its mods are checking regularly anymore. > > ####**Less resistant to DDoS attacks and spam** > > Like all networks with low transaction fees, it's at risk of DDoS attacks. > > In early Jan 2022, [Sunflowers Farm \(SFF\) unintentionally DDoS-attacked the Polygon PoS network](https://www.coindesk.com/tech/2022/01/06/polygon-under-accidental-attack-from-swarm-of-sunflower-farmers/) and completely congested the network because it was more profitable to play the game and spam transactions than pay network fees. Transaction fees shot up 20x. Eventually, a hacker exploited the SFF game and reduced its price to zero, and users rejoiced because it cleared the congestion. > > **It has a Gas Cartel** > > Spam attacks were eventually mitigated when the whole Polygon validator community chose to [lock priority fees at a 30 Gwei minimum](https://cryptoslate.com/polygon-matic-to-raise-gas-fee-to-30-gwei-to-prevent-spam-transactions/). That's not an offical part of protocol. Polygon validators have colluded off-chain and are running **gas cartel**, like OPEC. > > However, it still gets tons of spam transactions, which I have experienced first-hand many times. All my Polygon accounts with activity on them were randomly sent spam tokens and NFTs. Many of these tokens are part of scam that try to trick you into interacting with them by selling them. Other are advertising sketchy website links. > > This is the downside of having sub-penny transactions. > > ####**Still requires the Ethereum network** > > The Polygon PoS network is a side chain for Ethereum. Many parts of Polygon still require Ethereum and pay fees in ETH instead of MATIC. OpenSea's NFT are usually quoted in ETH instead of MATIC. The MATIC token its originates on Ethereum and is bridged over to Polygon PoS as an ERC-20 token. Staking is also done on the Ethereum mainnet. The periodic Polygon checkpoints require paying Ethereum fees too. > > Thus Polygon's success depends on Ethereum's success and security. > > Going from Layer 1 Ethereum to Polygon is mainly done through the Polygon PoS bridge, which costs Ethereum gas fees. The first time bridging over to Polygon can be stressful. Their documentation says it should only take [22-30 minutes](https://wiki.polygon.technology/docs/develop/ethereum-polygon/getting-started/) when it often takes many hours as many people including me have found out the hard way. > > ####**Numerous reorgs** > > Polygon has [multiple reorgs every day](https://polygonscan.com/blocks_forked). Many of these are of 10+ depths, which is dangerously high. Due to reorgs, transactions up to 32 blocks ago can be completely reversed. In fact, up until the Delhi update (Jan 17, 2023), it was common to see reorgs up to 128-blocks ago (5 minutes). After the update, this has been reduced to a max of 32 blocks (1 minute). That's better than before the update, but it's still a lot. The reason behind this unique and dangerous Polygon phenomenon is due to the validator sprints that it uses on the Bor block production layer. [I wrote a separate article to explain this phenomenon](https://mplankton.substack.com/p/polygons-block-reorg-problem). > > Even after the Delhi update, there was still a massive [153-block reorg in Feb 2023](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/) and multiple-validator outage caused by an unrelated bug. > > ####**Centralization concerns** > > **Pausable tokens** > > The [MATIC token contract](https://etherscan.io/token/0x7d1afa7b718fb893db30a3abc0cfc608aacfebb0#code) is pausable. There is a private list of addresses (stored in the "_pausers" private role) that can unilaterally pause the entire MATIC token without needing any other members to approve. > > **Centralized control of Polygon contracts on Ethereum mainnet via its Multisig owner account** > > At any given time, Polygon can update its contracts using this Multisig Gnosis Safe, and it has already done so **40 times in the past year** and 170 times in the past 2 years. That's a lot of unannounced updates. > > It does this through a [5 out of 9 Multisig Gnosis Safe](https://etherscan.io/address/0xfa7d2a996ac6350f4b56c043112da0366a59b74c) (often misquoted as an 5 out of 8 Multisig) that controls all of Polygon's contracts on Ethereum (e.g. Plasma Bridge, PoS Bridge, Staking Contract, Governance Proxy, Ether Bridge, Root Chain Proxy, Polygon-to-Ethereum token mapping, and many other contracts). 4 of these owners are Polygon members, 4 are external DeFi users, and 1 is an unknown account (possibly the owner of Quickswap). > > **[My own investigation](https://mplankton.substack.com/p/investigating-the-59-polygon-multisig) discovered that this MultiSig account is one of the worst-documented parts of Polygon**: > > * Every media site, blog, and forum to this day still thinks it's an 5/8 Multisig based on an old letter back in May 2021. The fact that no one has mentioned the 9th owner (added 2 years ago) is a strong sign the public isn't actually auditing the Polygon admin actions on that Multisig contract. > * A 9th owner was added back [in June 2021](https://etherscan.io/tx/0xb02b91300e3cea5bb788513cd858f27f27410b3bc67b8e12dca10944b4d611c8) **unannounced**. An additional 2 Polygon owners were swapped in the past year **unannounced**. > * [Back in Aug 2021](https://etherscan.io/tx/0x9eca1e21c66d7a30bfb69dedb0857314cf7ed127d149328d518678f7e22fbdb9), ownership of all Polygon's contracts were replaced by a [TimeLock contract](https://etherscan.io/address/0xCaf0aa768A3AE1297DF20072419Db8Bb8b5C8cEf). This Timelock provides an acceptance window where any action on Polygon's contracts has to wait 48 hours before it takes effect. The Timelock is in turn controlled by the 5/9 Gnosis Safe account. > * Polygon's websites, forums, Discord channel, and subreddit don't mention the Timelock. > * **Even Polygon's own documentation team is unaware of the Timelock.** There is [one document that mentions the Multisig address](https://wiki.polygon.technology/docs/faq/commit-chain-multisigs/) suggests that a Timelock is a future update, when it's actually already active. > > ####**Upgrade process is centralized** > > Polygon Labs controls the upgrade process through centralized governance. > > Back in Dec 2021, the Polygon team [secretly hard-forked the network](https://cryptobriefing.com/a-hacker-stole-1-6m-after-exploiting-a-polygon-bug/) by pushing out a patch 1 day after a hacker stole $1.6M from the network from the Polygon PoS genesis contract in Dec 2021. The team didn't publicize the reason for the emergency patch until over 3 weeks later. > > In Jan 2023, the **Delhi Hardfork, PIP-7**, was voted on by only [15 out of 100 non-dev validators](https://forum.polygon.technology/t/pre-pip-discussion-addressing-reorgs-and-gas-spikes/10623). The vote was only used as non-binding feedback, so Polygon Lab devs still maintained real control over the upgrade. > > In Feb 2023, there was a client bug that caused [a multi-validator outage and 153-block reorg](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/). Due to the outage and slow syncing where many out-of-sync validators were taking up to a day to resync, many of them were missing their 98% checkpoint SLA requirements for staying on as a validator. As a result, the Polygon team pushed **an emergency proposal, PIP-9**, to reduce the threshold back to 95%. In less than half a day, it passed and was activated. Even over 4 days, only 27 out of 100 validators had voted on it. > > **Future decentralized governance** > > It's been over a year since Polygon posted they were looking into [Governance Decentralization](https://blog.polygon.technology/state-of-governance-decentralization/). It wasn't until only Feb 2023 that they started the first steps towards decentralized governance via [PIP-1](https://forum.pol... ***** Would you like to learn more? Check out the [Cointest archive](/r/CointestOfficial/wiki/cointest_archive#wiki_Polygon) to find submissions for other topics.

CointestMod

#Polygon Con-Arguments Below is a Polygon con-argument written by a deleted user. > ####**Has plenty of competitors, including itself** > > Currently, Polygon PoS is competing against optimistic L2 blockchains like Arbitrum One and Optimism. Arbitrum has nearly [2x the TVL as Polygon](https://defillama.com/chains), and Optimism has almost caught up. > > Polygon's future zkEVM rollup is also competing against other zkEVM rollups. Once its zkEVM is released, it's possible it's going to split the Polygon community between those who want to stay on the sidechain and those who want to use the zkEVM. **If you look at their [zkEVM testnet](https://explorer.public.zkevm-test.net/txs?block_number=143530&index=0&page_number=1&page_size=50&pages_limit=200), fees are paid in Ether, not MATIC.** That's bearish for MATIC token utility. > > **TVL has dropped considerably compared to L2s** > > One year ago back in Jan 2022, [Polygon TVL was $4.8B USD](https://defillama.com/chain/Polygon) while the combined [Layer 2 rollup TVL was $5.4B USD](https://l2beat.com/scaling/tvl). While L2 TVL has increased a little despite the bear market, Polygon's TVL has collapsed by 75% to $1.2B. > > **Growing dApp competition from L2 rollups** > > A year ago, Polygon PoS was unique in that it was the only network besides Ethereum that had OpenSea support. Now OpenSea supports a dozen different networks, including competing Layer 2 rollups networks like Optimism, Arbitrum One, and even Arbitrum Nova. So there's a lot more competition. > > **Declining social media support** > > With L2 rollups developing so quickly, many in the Ethereum community have turned against Polygon, creating a narrative that it's "just a sidechain", not a true Layer 2. > > The 0xPolygon subreddit has become more of a ghost town with noticeable amounts of spam posts. I don't think its mods are checking regularly anymore. > > ####**Less resistant to DDoS attacks and spam** > > Like all networks with low transaction fees, it's at risk of DDoS attacks. > > In early Jan 2022, [Sunflowers Farm \(SFF\) unintentionally DDoS-attacked the Polygon PoS network](https://www.coindesk.com/tech/2022/01/06/polygon-under-accidental-attack-from-swarm-of-sunflower-farmers/) and completely congested the network because it was more profitable to play the game and spam transactions than pay network fees. Transaction fees shot up 20x. Eventually, a hacker exploited the SFF game and reduced its price to zero, and users rejoiced because it cleared the congestion. > > **It has a Gas Cartel** > > Spam attacks were eventually mitigated when the whole Polygon validator community chose to [lock priority fees at a 30 Gwei minimum](https://cryptoslate.com/polygon-matic-to-raise-gas-fee-to-30-gwei-to-prevent-spam-transactions/). That's not an offical part of protocol. Polygon validators have colluded off-chain and are running **gas cartel**, like OPEC. > > However, it still gets tons of spam transactions, which I have experienced first-hand many times. All my Polygon accounts with activity on them were randomly sent spam tokens and NFTs. Many of these tokens are part of scam that try to trick you into interacting with them by selling them. Other are advertising sketchy website links. > > This is the downside of having sub-penny transactions. > > ####**Still requires the Ethereum network** > > The Polygon PoS network is a side chain for Ethereum. Many parts of Polygon still require Ethereum and pay fees in ETH instead of MATIC. OpenSea's NFT are usually quoted in ETH instead of MATIC. The MATIC token its originates on Ethereum and is bridged over to Polygon PoS as an ERC-20 token. Staking is also done on the Ethereum mainnet. The periodic Polygon checkpoints require paying Ethereum fees too. > > Thus Polygon's success depends on Ethereum's success and security. > > Going from Layer 1 Ethereum to Polygon is mainly done through the Polygon PoS bridge, which costs Ethereum gas fees. The first time bridging over to Polygon can be stressful. Their documentation says it should only take [22-30 minutes](https://wiki.polygon.technology/docs/develop/ethereum-polygon/getting-started/) when it often takes many hours as many people including me have found out the hard way. > > ####**Numerous reorgs** > > Polygon has [multiple reorgs every day](https://polygonscan.com/blocks_forked). Many of these are of 10+ depths, which is dangerously high. Due to reorgs, transactions up to 32 blocks ago can be completely reversed. In fact, up until the Delhi update (Jan 17, 2023), it was common to see reorgs up to 128-blocks ago (5 minutes). After the update, this has been reduced to a max of 32 blocks (1 minute). That's better than before the update, but it's still a lot. The reason behind this unique and dangerous Polygon phenomenon is due to the validator sprints that it uses on the Bor block production layer. [I wrote a separate article to explain this phenomenon](https://mplankton.substack.com/p/polygons-block-reorg-problem). > > Even after the Delhi update, there was still a massive [153-block reorg in Feb 2023](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/) and multiple-validator outage caused by an unrelated bug. > > ####**Centralization concerns** > > **Pausable tokens** > > The [MATIC token contract](https://etherscan.io/token/0x7d1afa7b718fb893db30a3abc0cfc608aacfebb0#code) is pausable. There is a private list of addresses (stored in the "_pausers" private role) that can unilaterally pause the entire MATIC token without needing any other members to approve. > > **Centralized control of Polygon contracts on Ethereum mainnet via its Multisig owner account** > > At any given time, Polygon can update its contracts using this Multisig Gnosis Safe, and it has already done so **40 times in the past year** and 170 times in the past 2 years. That's a lot of unannounced updates. > > It does this through a [5 out of 9 Multisig Gnosis Safe](https://etherscan.io/address/0xfa7d2a996ac6350f4b56c043112da0366a59b74c) (often misquoted as an 5 out of 8 Multisig) that controls all of Polygon's contracts on Ethereum (e.g. Plasma Bridge, PoS Bridge, Staking Contract, Governance Proxy, Ether Bridge, Root Chain Proxy, Polygon-to-Ethereum token mapping, and many other contracts). 4 of these owners are Polygon members, 4 are external DeFi users, and 1 is an unknown account (possibly the owner of Quickswap). > > **[My own investigation](https://mplankton.substack.com/p/investigating-the-59-polygon-multisig) discovered that this MultiSig account is one of the worst-documented parts of Polygon**: > > * Every media site, blog, and forum to this day still thinks it's an 5/8 Multisig based on an old letter back in May 2021. The fact that no one has mentioned the 9th owner (added 2 years ago) is a strong sign the public isn't actually auditing the Polygon admin actions on that Multisig contract. > * A 9th owner was added back [in June 2021](https://etherscan.io/tx/0xb02b91300e3cea5bb788513cd858f27f27410b3bc67b8e12dca10944b4d611c8) **unannounced**. An additional 2 Polygon owners were swapped in the past year **unannounced**. > * [Back in Aug 2021](https://etherscan.io/tx/0x9eca1e21c66d7a30bfb69dedb0857314cf7ed127d149328d518678f7e22fbdb9), ownership of all Polygon's contracts were replaced by a [TimeLock contract](https://etherscan.io/address/0xCaf0aa768A3AE1297DF20072419Db8Bb8b5C8cEf). This Timelock provides an acceptance window where any action on Polygon's contracts has to wait 48 hours before it takes effect. The Timelock is in turn controlled by the 5/9 Gnosis Safe account. > * Polygon's websites, forums, Discord channel, and subreddit don't mention the Timelock. > * **Even Polygon's own documentation team is unaware of the Timelock.** There is [one document that mentions the Multisig address](https://wiki.polygon.technology/docs/faq/commit-chain-multisigs/) suggests that a Timelock is a future update, when it's actually already active. > > ####**Upgrade process is centralized** > > Polygon Labs controls the upgrade process through centralized governance. > > Back in Dec 2021, the Polygon team [secretly hard-forked the network](https://cryptobriefing.com/a-hacker-stole-1-6m-after-exploiting-a-polygon-bug/) by pushing out a patch 1 day after a hacker stole $1.6M from the network from the Polygon PoS genesis contract in Dec 2021. The team didn't publicize the reason for the emergency patch until over 3 weeks later. > > In Jan 2023, the **Delhi Hardfork, PIP-7**, was voted on by only [15 out of 100 non-dev validators](https://forum.polygon.technology/t/pre-pip-discussion-addressing-reorgs-and-gas-spikes/10623). The vote was only used as non-binding feedback, so Polygon Lab devs still maintained real control over the upgrade. > > In Feb 2023, there was a client bug that caused [a multi-validator outage and 153-block reorg](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/). Due to the outage and slow syncing where many out-of-sync validators were taking up to a day to resync, many of them were missing their 98% checkpoint SLA requirements for staying on as a validator. As a result, the Polygon team pushed **an emergency proposal, PIP-9**, to reduce the threshold back to 95%. In less than half a day, it passed and was activated. Even over 4 days, only 27 out of 100 validators had voted on it. > > **Future decentralized governance** > > It's been over a year since Polygon posted they were looking into [Governance Decentralization](https://blog.polygon.technology/state-of-governance-decentralization/). It wasn't until only Feb 2023 that they started the first steps towards decentralized governance via [PIP-1](https://forum.pol... ***** Would you like to learn more? Check out the [Cointest archive](/r/CointestOfficial/wiki/cointest_archive#wiki_Polygon) to find submissions for other topics.

Alternative_Ear_7256

You couldn’t have said it any better. By far the best telegram community I’ve been in with absolutely hilarious memes $SEAT🪑 

rocketsoar

My dream is to have a lambo, pls help me !! 0x6d42ccA5DC590AE6195e5ce2b6363e0B0bdE2bdF

xeroc

Bitshares 7 years ago: 60k ops per second https://github.com/dily3825002/awesome-blockchain/blob/master/%E7%99%BD%E7%9A%AE%E4%B9%A6/bitshares-stresstest.pdf

ImKindaNiceSometimes

I think doing your own dice rolls to find your keys for your new wallet could provide a sense of comfort. Knowing without a shadow of a doubt that no one else could possibly know your seed words is a wonderful feeling. This video shows how two unrelated hardware wallets will generate the same exact seed words if the same dice rolls are recorded on both hardware devices. https://youtu.be/qxOhCvot77I?si=0pJVyf5yt-WGu8AE I would practice a few small transactions both sending and receiving but always keeping your keys offline and air gapped - never ever take a photo of them, never put them in Google drive, etc.

Hellonbyebye

Bitcoin has no issue with big transaction. For smaller transaction there are many options: centralised -maybe visa mastercard AE will adopt btc, decentralised - lightning, semi decentralised liquid fedimint

Corbimos

Bitcoin is the UTXO set built by my node. My node checks other nodes to make sure they see the same thing. My private keys allow me to modify that UTXO set and broadcast to others. All of this is local to me. Saying bitcoin is "on the cloud" is subjective as bitcoin is really the sum of all the nodes doing local verification, not "the cloud". > And, a cloud wallet where only you (the owner) has the keys and access to. So you're asking the difference between a hot wallet and a cold wallet? https://youtu.be/Aji_E9sw0AE?si=FS9-_wh1Dg85aAl_ What does the "cloud" have to do with it? Is someone else storing your keys? Remember, "the cloud" is just someone else's computer you're accessing over the internet.

CointestMod

#Polygon Con-Arguments Below is a Polygon con-argument written by a deleted user. > ####**Has plenty of competitors, including itself** > > Currently, Polygon PoS is competing against optimistic L2 blockchains like Arbitrum One and Optimism. Arbitrum has nearly [2x the TVL as Polygon](https://defillama.com/chains), and Optimism has almost caught up. > > Polygon's future zkEVM rollup is also competing against other zkEVM rollups. Once its zkEVM is released, it's possible it's going to split the Polygon community between those who want to stay on the sidechain and those who want to use the zkEVM. **If you look at their [zkEVM testnet](https://explorer.public.zkevm-test.net/txs?block_number=143530&index=0&page_number=1&page_size=50&pages_limit=200), fees are paid in Ether, not MATIC.** That's bearish for MATIC token utility. > > **TVL has dropped considerably compared to L2s** > > One year ago back in Jan 2022, [Polygon TVL was $4.8B USD](https://defillama.com/chain/Polygon) while the combined [Layer 2 rollup TVL was $5.4B USD](https://l2beat.com/scaling/tvl). While L2 TVL has increased a little despite the bear market, Polygon's TVL has collapsed by 75% to $1.2B. > > **Growing dApp competition from L2 rollups** > > A year ago, Polygon PoS was unique in that it was the only network besides Ethereum that had OpenSea support. Now OpenSea supports a dozen different networks, including competing Layer 2 rollups networks like Optimism, Arbitrum One, and even Arbitrum Nova. So there's a lot more competition. > > **Declining social media support** > > With L2 rollups developing so quickly, many in the Ethereum community have turned against Polygon, creating a narrative that it's "just a sidechain", not a true Layer 2. > > The 0xPolygon subreddit has become more of a ghost town with noticeable amounts of spam posts. I don't think its mods are checking regularly anymore. > > ####**Less resistant to DDoS attacks and spam** > > Like all networks with low transaction fees, it's at risk of DDoS attacks. > > In early Jan 2022, [Sunflowers Farm \(SFF\) unintentionally DDoS-attacked the Polygon PoS network](https://www.coindesk.com/tech/2022/01/06/polygon-under-accidental-attack-from-swarm-of-sunflower-farmers/) and completely congested the network because it was more profitable to play the game and spam transactions than pay network fees. Transaction fees shot up 20x. Eventually, a hacker exploited the SFF game and reduced its price to zero, and users rejoiced because it cleared the congestion. > > **It has a Gas Cartel** > > Spam attacks were eventually mitigated when the whole Polygon validator community chose to [lock priority fees at a 30 Gwei minimum](https://cryptoslate.com/polygon-matic-to-raise-gas-fee-to-30-gwei-to-prevent-spam-transactions/). That's not an offical part of protocol. Polygon validators have colluded off-chain and are running **gas cartel**, like OPEC. > > However, it still gets tons of spam transactions, which I have experienced first-hand many times. All my Polygon accounts with activity on them were randomly sent spam tokens and NFTs. Many of these tokens are part of scam that try to trick you into interacting with them by selling them. Other are advertising sketchy website links. > > This is the downside of having sub-penny transactions. > > ####**Still requires the Ethereum network** > > The Polygon PoS network is a side chain for Ethereum. Many parts of Polygon still require Ethereum and pay fees in ETH instead of MATIC. OpenSea's NFT are usually quoted in ETH instead of MATIC. The MATIC token its originates on Ethereum and is bridged over to Polygon PoS as an ERC-20 token. Staking is also done on the Ethereum mainnet. The periodic Polygon checkpoints require paying Ethereum fees too. > > Thus Polygon's success depends on Ethereum's success and security. > > Going from Layer 1 Ethereum to Polygon is mainly done through the Polygon PoS bridge, which costs Ethereum gas fees. The first time bridging over to Polygon can be stressful. Their documentation says it should only take [22-30 minutes](https://wiki.polygon.technology/docs/develop/ethereum-polygon/getting-started/) when it often takes many hours as many people including me have found out the hard way. > > ####**Numerous reorgs** > > Polygon has [multiple reorgs every day](https://polygonscan.com/blocks_forked). Many of these are of 10+ depths, which is dangerously high. Due to reorgs, transactions up to 32 blocks ago can be completely reversed. In fact, up until the Delhi update (Jan 17, 2023), it was common to see reorgs up to 128-blocks ago (5 minutes). After the update, this has been reduced to a max of 32 blocks (1 minute). That's better than before the update, but it's still a lot. The reason behind this unique and dangerous Polygon phenomenon is due to the validator sprints that it uses on the Bor block production layer. [I wrote a separate article to explain this phenomenon](https://mplankton.substack.com/p/polygons-block-reorg-problem). > > Even after the Delhi update, there was still a massive [153-block reorg in Feb 2023](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/) and multiple-validator outage caused by an unrelated bug. > > ####**Centralization concerns** > > **Pausable tokens** > > The [MATIC token contract](https://etherscan.io/token/0x7d1afa7b718fb893db30a3abc0cfc608aacfebb0#code) is pausable. There is a private list of addresses (stored in the "_pausers" private role) that can unilaterally pause the entire MATIC token without needing any other members to approve. > > **Centralized control of Polygon contracts on Ethereum mainnet via its Multisig owner account** > > At any given time, Polygon can update its contracts using this Multisig Gnosis Safe, and it has already done so **40 times in the past year** and 170 times in the past 2 years. That's a lot of unannounced updates. > > It does this through a [5 out of 9 Multisig Gnosis Safe](https://etherscan.io/address/0xfa7d2a996ac6350f4b56c043112da0366a59b74c) (often misquoted as an 5 out of 8 Multisig) that controls all of Polygon's contracts on Ethereum (e.g. Plasma Bridge, PoS Bridge, Staking Contract, Governance Proxy, Ether Bridge, Root Chain Proxy, Polygon-to-Ethereum token mapping, and many other contracts). 4 of these owners are Polygon members, 4 are external DeFi users, and 1 is an unknown account (possibly the owner of Quickswap). > > **[My own investigation](https://mplankton.substack.com/p/investigating-the-59-polygon-multisig) discovered that this MultiSig account is one of the worst-documented parts of Polygon**: > > * Every media site, blog, and forum to this day still thinks it's an 5/8 Multisig based on an old letter back in May 2021. The fact that no one has mentioned the 9th owner (added 2 years ago) is a strong sign the public isn't actually auditing the Polygon admin actions on that Multisig contract. > * A 9th owner was added back [in June 2021](https://etherscan.io/tx/0xb02b91300e3cea5bb788513cd858f27f27410b3bc67b8e12dca10944b4d611c8) **unannounced**. An additional 2 Polygon owners were swapped in the past year **unannounced**. > * [Back in Aug 2021](https://etherscan.io/tx/0x9eca1e21c66d7a30bfb69dedb0857314cf7ed127d149328d518678f7e22fbdb9), ownership of all Polygon's contracts were replaced by a [TimeLock contract](https://etherscan.io/address/0xCaf0aa768A3AE1297DF20072419Db8Bb8b5C8cEf). This Timelock provides an acceptance window where any action on Polygon's contracts has to wait 48 hours before it takes effect. The Timelock is in turn controlled by the 5/9 Gnosis Safe account. > * Polygon's websites, forums, Discord channel, and subreddit don't mention the Timelock. > * **Even Polygon's own documentation team is unaware of the Timelock.** There is [one document that mentions the Multisig address](https://wiki.polygon.technology/docs/faq/commit-chain-multisigs/) suggests that a Timelock is a future update, when it's actually already active. > > ####**Upgrade process is centralized** > > Polygon Labs controls the upgrade process through centralized governance. > > Back in Dec 2021, the Polygon team [secretly hard-forked the network](https://cryptobriefing.com/a-hacker-stole-1-6m-after-exploiting-a-polygon-bug/) by pushing out a patch 1 day after a hacker stole $1.6M from the network from the Polygon PoS genesis contract in Dec 2021. The team didn't publicize the reason for the emergency patch until over 3 weeks later. > > In Jan 2023, the **Delhi Hardfork, PIP-7**, was voted on by only [15 out of 100 non-dev validators](https://forum.polygon.technology/t/pre-pip-discussion-addressing-reorgs-and-gas-spikes/10623). The vote was only used as non-binding feedback, so Polygon Lab devs still maintained real control over the upgrade. > > In Feb 2023, there was a client bug that caused [a multi-validator outage and 153-block reorg](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/). Due to the outage and slow syncing where many out-of-sync validators were taking up to a day to resync, many of them were missing their 98% checkpoint SLA requirements for staying on as a validator. As a result, the Polygon team pushed **an emergency proposal, PIP-9**, to reduce the threshold back to 95%. In less than half a day, it passed and was activated. Even over 4 days, only 27 out of 100 validators had voted on it. > > **Future decentralized governance** > > It's been over a year since Polygon posted they were looking into [Governance Decentralization](https://blog.polygon.technology/state-of-governance-decentralization/). It wasn't until only Feb 2023 that they started the first steps towards decentralized governance via [PIP-1](https://forum.pol... ***** Would you like to learn more? Check out the [Cointest archive](/r/CointestOfficial/wiki/cointest_archive#wiki_Polygon) to find submissions for other topics.

CNNJDream

Thank you for your response. I apologize if my initial explanation was not clear enough. Allow me to provide more details about the underlying principles of Bitcoin addresses and the specific issue I am facing. In the Bitcoin system, an address is derived from a public key, which in turn is generated from a private key. The process typically follows these steps: A private key is generated, which is a random 256-bit number. The corresponding public key is derived from the private key using elliptic curve cryptography (specifically, the secp256k1 curve). The public key is then hashed using the SHA-256 and RIPEMD-160 algorithms to create a 160-bit hash. This hash is then encoded using Base58Check encoding, which includes a version byte and a checksum, resulting in the final Bitcoin address. In my case, an issue arose during step 2. When generating the public key, the first character of the first 32 hexadecimal characters of the public key was 0. This led to the first 8 bits of the public key being 0, effectively making it a 248-bit public key instead of the expected 256 bits. Despite this, the incorrect 248-bit public key was used to generate a Bitcoin address following steps 3 and 4. This address ended up receiving some bitcoins. Later, I used the same private key to generate the correct 256-bit public key and derived a different Bitcoin address from it. However, the bitcoins that were sent to the first address (derived from the incorrect 248-bit public key) are not accessible using the private key directly, as the Bitcoin system associates those funds with the incorrect public key and address. To further illustrate this, consider the two examples I provided: Example 1: PrivateKeyHexStr: 1D179D45DF2F02271CD4DAA1114B7226480BBF3DA62D94081CC6228C950F3300 Incorrect Public Key (248 bits): 2C3D118366F853F7A7FCD0E0506A87FD1ED7AD7E19103059A85C0FA8ADED85 Incorrect Address: 13mpPh9UMtSN54GTbjj4ht7S3hzCPhmmVA Example 2: PrivateKeyHexStr: 08C5F27C4B0522975583AE6BAE67B2155F5339BA040693335D4A2C4A0A213726 Incorrect Public Key (248 bits): BEC0F8B027D6333EFBBCC87ABD1C2912AB052DE99F391DB3E3EE1EF50708DD Incorrect Address: 14z6wZb4uGE1iT9osbQGMW75iNS1awCGSe In both cases, the incorrect public keys and addresses were generated due to the leading 0 in the public key, causing them to be 248 bits instead of 256 bits. I hope this clarifies the issue I am facing. I am looking for ways to recover the bitcoins that were sent to the addresses derived from these incorrect public keys, given that I have the corresponding private keys. If you have any further questions or need more information, please let me know. I greatly appreciate your interest and any help you can provide.

gulfbitcoin

According to a basic Google search: >Binance FZE is a free zone establishment, registered with the Dubai World Trade Centre (registration number 1693) with our registered offices at The Offices 4 - One Central, Dubai World Trade Centre, Floor 8, WeWork-08-161, Dubai, UAE. [https://www.binance.com/en-AE/terms](https://www.binance.com/en-AE/terms)

CointestMod

#Polygon Con-Arguments Below is a Polygon con-argument written by a deleted user. > ####**Has plenty of competitors, including itself** > > Currently, Polygon PoS is competing against optimistic L2 blockchains like Arbitrum One and Optimism. Arbitrum has nearly [2x the TVL as Polygon](https://defillama.com/chains), and Optimism has almost caught up. > > Polygon's future zkEVM rollup is also competing against other zkEVM rollups. Once its zkEVM is released, it's possible it's going to split the Polygon community between those who want to stay on the sidechain and those who want to use the zkEVM. **If you look at their [zkEVM testnet](https://explorer.public.zkevm-test.net/txs?block_number=143530&index=0&page_number=1&page_size=50&pages_limit=200), fees are paid in Ether, not MATIC.** That's bearish for MATIC token utility. > > **TVL has dropped considerably compared to L2s** > > One year ago back in Jan 2022, [Polygon TVL was $4.8B USD](https://defillama.com/chain/Polygon) while the combined [Layer 2 rollup TVL was $5.4B USD](https://l2beat.com/scaling/tvl). While L2 TVL has increased a little despite the bear market, Polygon's TVL has collapsed by 75% to $1.2B. > > **Growing dApp competition from L2 rollups** > > A year ago, Polygon PoS was unique in that it was the only network besides Ethereum that had OpenSea support. Now OpenSea supports a dozen different networks, including competing Layer 2 rollups networks like Optimism, Arbitrum One, and even Arbitrum Nova. So there's a lot more competition. > > **Declining social media support** > > With L2 rollups developing so quickly, many in the Ethereum community have turned against Polygon, creating a narrative that it's "just a sidechain", not a true Layer 2. > > The 0xPolygon subreddit has become more of a ghost town with noticeable amounts of spam posts. I don't think its mods are checking regularly anymore. > > ####**Less resistant to DDoS attacks and spam** > > Like all networks with low transaction fees, it's at risk of DDoS attacks. > > In early Jan 2022, [Sunflowers Farm \(SFF\) unintentionally DDoS-attacked the Polygon PoS network](https://www.coindesk.com/tech/2022/01/06/polygon-under-accidental-attack-from-swarm-of-sunflower-farmers/) and completely congested the network because it was more profitable to play the game and spam transactions than pay network fees. Transaction fees shot up 20x. Eventually, a hacker exploited the SFF game and reduced its price to zero, and users rejoiced because it cleared the congestion. > > **It has a Gas Cartel** > > Spam attacks were eventually mitigated when the whole Polygon validator community chose to [lock priority fees at a 30 Gwei minimum](https://cryptoslate.com/polygon-matic-to-raise-gas-fee-to-30-gwei-to-prevent-spam-transactions/). That's not an offical part of protocol. Polygon validators have colluded off-chain and are running **gas cartel**, like OPEC. > > However, it still gets tons of spam transactions, which I have experienced first-hand many times. All my Polygon accounts with activity on them were randomly sent spam tokens and NFTs. Many of these tokens are part of scam that try to trick you into interacting with them by selling them. Other are advertising sketchy website links. > > This is the downside of having sub-penny transactions. > > ####**Still requires the Ethereum network** > > The Polygon PoS network is a side chain for Ethereum. Many parts of Polygon still require Ethereum and pay fees in ETH instead of MATIC. OpenSea's NFT are usually quoted in ETH instead of MATIC. The MATIC token its originates on Ethereum and is bridged over to Polygon PoS as an ERC-20 token. Staking is also done on the Ethereum mainnet. The periodic Polygon checkpoints require paying Ethereum fees too. > > Thus Polygon's success depends on Ethereum's success and security. > > Going from Layer 1 Ethereum to Polygon is mainly done through the Polygon PoS bridge, which costs Ethereum gas fees. The first time bridging over to Polygon can be stressful. Their documentation says it should only take [22-30 minutes](https://wiki.polygon.technology/docs/develop/ethereum-polygon/getting-started/) when it often takes many hours as many people including me have found out the hard way. > > ####**Numerous reorgs** > > Polygon has [multiple reorgs every day](https://polygonscan.com/blocks_forked). Many of these are of 10+ depths, which is dangerously high. Due to reorgs, transactions up to 32 blocks ago can be completely reversed. In fact, up until the Delhi update (Jan 17, 2023), it was common to see reorgs up to 128-blocks ago (5 minutes). After the update, this has been reduced to a max of 32 blocks (1 minute). That's better than before the update, but it's still a lot. The reason behind this unique and dangerous Polygon phenomenon is due to the validator sprints that it uses on the Bor block production layer. [I wrote a separate article to explain this phenomenon](https://mplankton.substack.com/p/polygons-block-reorg-problem). > > Even after the Delhi update, there was still a massive [153-block reorg in Feb 2023](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/) and multiple-validator outage caused by an unrelated bug. > > ####**Centralization concerns** > > **Pausable tokens** > > The [MATIC token contract](https://etherscan.io/token/0x7d1afa7b718fb893db30a3abc0cfc608aacfebb0#code) is pausable. There is a private list of addresses (stored in the "_pausers" private role) that can unilaterally pause the entire MATIC token without needing any other members to approve. > > **Centralized control of Polygon contracts on Ethereum mainnet via its Multisig owner account** > > At any given time, Polygon can update its contracts using this Multisig Gnosis Safe, and it has already done so **40 times in the past year** and 170 times in the past 2 years. That's a lot of unannounced updates. > > It does this through a [5 out of 9 Multisig Gnosis Safe](https://etherscan.io/address/0xfa7d2a996ac6350f4b56c043112da0366a59b74c) (often misquoted as an 5 out of 8 Multisig) that controls all of Polygon's contracts on Ethereum (e.g. Plasma Bridge, PoS Bridge, Staking Contract, Governance Proxy, Ether Bridge, Root Chain Proxy, Polygon-to-Ethereum token mapping, and many other contracts). 4 of these owners are Polygon members, 4 are external DeFi users, and 1 is an unknown account (possibly the owner of Quickswap). > > **[My own investigation](https://mplankton.substack.com/p/investigating-the-59-polygon-multisig) discovered that this MultiSig account is one of the worst-documented parts of Polygon**: > > * Every media site, blog, and forum to this day still thinks it's an 5/8 Multisig based on an old letter back in May 2021. The fact that no one has mentioned the 9th owner (added 2 years ago) is a strong sign the public isn't actually auditing the Polygon admin actions on that Multisig contract. > * A 9th owner was added back [in June 2021](https://etherscan.io/tx/0xb02b91300e3cea5bb788513cd858f27f27410b3bc67b8e12dca10944b4d611c8) **unannounced**. An additional 2 Polygon owners were swapped in the past year **unannounced**. > * [Back in Aug 2021](https://etherscan.io/tx/0x9eca1e21c66d7a30bfb69dedb0857314cf7ed127d149328d518678f7e22fbdb9), ownership of all Polygon's contracts were replaced by a [TimeLock contract](https://etherscan.io/address/0xCaf0aa768A3AE1297DF20072419Db8Bb8b5C8cEf). This Timelock provides an acceptance window where any action on Polygon's contracts has to wait 48 hours before it takes effect. The Timelock is in turn controlled by the 5/9 Gnosis Safe account. > * Polygon's websites, forums, Discord channel, and subreddit don't mention the Timelock. > * **Even Polygon's own documentation team is unaware of the Timelock.** There is [one document that mentions the Multisig address](https://wiki.polygon.technology/docs/faq/commit-chain-multisigs/) suggests that a Timelock is a future update, when it's actually already active. > > ####**Upgrade process is centralized** > > Polygon Labs controls the upgrade process through centralized governance. > > Back in Dec 2021, the Polygon team [secretly hard-forked the network](https://cryptobriefing.com/a-hacker-stole-1-6m-after-exploiting-a-polygon-bug/) by pushing out a patch 1 day after a hacker stole $1.6M from the network from the Polygon PoS genesis contract in Dec 2021. The team didn't publicize the reason for the emergency patch until over 3 weeks later. > > In Jan 2023, the **Delhi Hardfork, PIP-7**, was voted on by only [15 out of 100 non-dev validators](https://forum.polygon.technology/t/pre-pip-discussion-addressing-reorgs-and-gas-spikes/10623). The vote was only used as non-binding feedback, so Polygon Lab devs still maintained real control over the upgrade. > > In Feb 2023, there was a client bug that caused [a multi-validator outage and 153-block reorg](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/). Due to the outage and slow syncing where many out-of-sync validators were taking up to a day to resync, many of them were missing their 98% checkpoint SLA requirements for staying on as a validator. As a result, the Polygon team pushed **an emergency proposal, PIP-9**, to reduce the threshold back to 95%. In less than half a day, it passed and was activated. Even over 4 days, only 27 out of 100 validators had voted on it. > > **Future decentralized governance** > > It's been over a year since Polygon posted they were looking into [Governance Decentralization](https://blog.polygon.technology/state-of-governance-decentralization/). It wasn't until only Feb 2023 that they started the first steps towards decentralized governance via [PIP-1](https://forum.pol... ***** Would you like to learn more? Check out the [Cointest archive](/r/CointestOfficial/wiki/cointest_archive#wiki_Polygon) to find submissions for other topics.

HSuke

That's an approval transaction. You gave 0x46ee2eefdce877532125d989b90ce41cdec5ebd4 permissions to spend up to 10^42 of your FET tokens And a minute later, they sent 138 of your FET tokens to 0x4A42AE14650771026d49d64b3b4A29dc030ecc63 https://etherscan.io/tx/0x588da7f9ff1b5f406da27c7d9961eeb6507f6231e6f0ae51981cb3b7b22d6534 You no longer have any FET tokens under your account.

Sir_McFuckington

1. 110,621 2. 0xd08b3236b42240CD6adc46afd155AE104f8eFD8f

TotallyNotANugget

1. 524,789 2. 0x9C6686AE3E043c139b4b0A7f695E25A2040b006F

stateofbidet

1. 555,555 2. 0x10AD1213FAeEf6E280b5C82AE94B8e177698218B

clean_cut89

1. 420,000 2. 0xEB977e30FF5f94bFDfdFdA90b25450AE06Bf7940

Maritzsa

520,465 0x57f471b05bbB08E22b0b710D0AE90D1217cb07B6

0regonja

690690 0xB4Bd807C9cDde19AE1498c7b7006713268E25997

slywalkers

330,000 0x2F4eb00990282Cfd9886D372AAa45a85781AE9bB

See0tter

1. 70721 2. 0xd47a0Aa24a1c0ABb188aF88d6Cc163AE740A8D65

Pleasant_Ad5360

203,111 0x9AE1c1Fd6Ba118253b99d8c5C36984B25d7537AD

diamondhands95

725000 0x5eE9d3E7CAC743278CC92539F0C77CeABE309AE6

ImaFreemason

17386 0x8E02AE7D33359728Fd7aCb439A28BC23F024A0E5

SimpleInsect8465

Any Inu EVM (ETH, ARB, OP, BASE, BSC, FTM, AVAX, MATIC):   0x2598c30330D5771AE9F983979209486aE26dE875 SOL: ACeWC77UeW2DBZMe7YBsuXoxLvk4dHMnPzneApau1Au6 Blast: 0x764933fbad8f5d04ccd088602096655c2ed9879f （一个月合并到E875统一合约） DogNexus404  ETH:   0x8B42DD505b2b4c0b21F75eb284c7295bC71E580B

doingbobthings

Good question! There are other rigs, like the [HeatBit ](https://heatbit.com/products/heatbit-mini-pro)and [Mars Lander](https://bitcoinmerch.com/products/bitcoin-merch%C2%AE-mars-lander-solo-bitcoin-miner-up-to-250gh-s) that supposedly 'mine' BTC, but I question how effective they are given the formidable computing power required to mine even just one Bitcoin.

Narrow_Room_4159

Usernames Aitsara1992 0x04b6d65AE021C52910d68fc467F4e103F0f2b8ec

CatTypedThisName

I got a lump sum payment in the middle of the pandemic. I knew it was a once in a lifetime thing. If you're not careful it will disappear. First thing you if you don't want to look back on this and consider it wasted: * How did you get this money? Set aside money for taxes, at least 20% of the payment, 35k * Count up all expenses plus and multiply by 6, store this in a liquid savings account that you can access. This is for emergencies and nothing else. Lets say that's 30k. * Now you have 110k, if you want one whole coin, either DCA your cash over the next few months or just lump sum it. I did a bit of both. * Now you have 60k\~ left, I would advise you to diversify your portfolio by lump summing or dollar cost averaging into a brokerage account using the [Boglehead Method](https://www.bogleheads.org/wiki/Bogleheads%C2%AE_investing_start-up_kit#Portfolio_construction). I use and like Vanguard. I know folks here may not because of their resistance to BTC. * Once the rest is done, treat yourself to a nice dinner, an experience or a gadget you want, etc. Make sure to enjoy a little bit of it to make the responsibility worth it. The TLDR is to divide your investment portfolio amongst a well diversified class of stocks, bonds and assets. Bitcoin is one way you'll diversify your portfolio. Once you've got your capital split between a few different areas, just keep DCA'ing into these accounts every pay period. I put cash into vanguard and btc on a regular basis.

CointestMod

#Polygon Con-Arguments Below is a Polygon con-argument written by a deleted user. > ####**Has plenty of competitors, including itself** > > Currently, Polygon PoS is competing against optimistic L2 blockchains like Arbitrum One and Optimism. Arbitrum has nearly [2x the TVL as Polygon](https://defillama.com/chains), and Optimism has almost caught up. > > Polygon's future zkEVM rollup is also competing against other zkEVM rollups. Once its zkEVM is released, it's possible it's going to split the Polygon community between those who want to stay on the sidechain and those who want to use the zkEVM. **If you look at their [zkEVM testnet](https://explorer.public.zkevm-test.net/txs?block_number=143530&index=0&page_number=1&page_size=50&pages_limit=200), fees are paid in Ether, not MATIC.** That's bearish for MATIC token utility. > > **TVL has dropped considerably compared to L2s** > > One year ago back in Jan 2022, [Polygon TVL was $4.8B USD](https://defillama.com/chain/Polygon) while the combined [Layer 2 rollup TVL was $5.4B USD](https://l2beat.com/scaling/tvl). While L2 TVL has increased a little despite the bear market, Polygon's TVL has collapsed by 75% to $1.2B. > > **Growing dApp competition from L2 rollups** > > A year ago, Polygon PoS was unique in that it was the only network besides Ethereum that had OpenSea support. Now OpenSea supports a dozen different networks, including competing Layer 2 rollups networks like Optimism, Arbitrum One, and even Arbitrum Nova. So there's a lot more competition. > > **Declining social media support** > > With L2 rollups developing so quickly, many in the Ethereum community have turned against Polygon, creating a narrative that it's "just a sidechain", not a true Layer 2. > > The 0xPolygon subreddit has become more of a ghost town with noticeable amounts of spam posts. I don't think its mods are checking regularly anymore. > > ####**Less resistant to DDoS attacks and spam** > > Like all networks with low transaction fees, it's at risk of DDoS attacks. > > In early Jan 2022, [Sunflowers Farm \(SFF\) unintentionally DDoS-attacked the Polygon PoS network](https://www.coindesk.com/tech/2022/01/06/polygon-under-accidental-attack-from-swarm-of-sunflower-farmers/) and completely congested the network because it was more profitable to play the game and spam transactions than pay network fees. Transaction fees shot up 20x. Eventually, a hacker exploited the SFF game and reduced its price to zero, and users rejoiced because it cleared the congestion. > > **It has a Gas Cartel** > > Spam attacks were eventually mitigated when the whole Polygon validator community chose to [lock priority fees at a 30 Gwei minimum](https://cryptoslate.com/polygon-matic-to-raise-gas-fee-to-30-gwei-to-prevent-spam-transactions/). That's not an offical part of protocol. Polygon validators have colluded off-chain and are running **gas cartel**, like OPEC. > > However, it still gets tons of spam transactions, which I have experienced first-hand many times. All my Polygon accounts with activity on them were randomly sent spam tokens and NFTs. Many of these tokens are part of scam that try to trick you into interacting with them by selling them. Other are advertising sketchy website links. > > This is the downside of having sub-penny transactions. > > ####**Still requires the Ethereum network** > > The Polygon PoS network is a side chain for Ethereum. Many parts of Polygon still require Ethereum and pay fees in ETH instead of MATIC. OpenSea's NFT are usually quoted in ETH instead of MATIC. The MATIC token its originates on Ethereum and is bridged over to Polygon PoS as an ERC-20 token. Staking is also done on the Ethereum mainnet. The periodic Polygon checkpoints require paying Ethereum fees too. > > Thus Polygon's success depends on Ethereum's success and security. > > Going from Layer 1 Ethereum to Polygon is mainly done through the Polygon PoS bridge, which costs Ethereum gas fees. The first time bridging over to Polygon can be stressful. Their documentation says it should only take [22-30 minutes](https://wiki.polygon.technology/docs/develop/ethereum-polygon/getting-started/) when it often takes many hours as many people including me have found out the hard way. > > ####**Numerous reorgs** > > Polygon has [multiple reorgs every day](https://polygonscan.com/blocks_forked). Many of these are of 10+ depths, which is dangerously high. Due to reorgs, transactions up to 32 blocks ago can be completely reversed. In fact, up until the Delhi update (Jan 17, 2023), it was common to see reorgs up to 128-blocks ago (5 minutes). After the update, this has been reduced to a max of 32 blocks (1 minute). That's better than before the update, but it's still a lot. The reason behind this unique and dangerous Polygon phenomenon is due to the validator sprints that it uses on the Bor block production layer. [I wrote a separate article to explain this phenomenon](https://mplankton.substack.com/p/polygons-block-reorg-problem). > > Even after the Delhi update, there was still a massive [153-block reorg in Feb 2023](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/) and multiple-validator outage caused by an unrelated bug. > > ####**Centralization concerns** > > **Pausable tokens** > > The [MATIC token contract](https://etherscan.io/token/0x7d1afa7b718fb893db30a3abc0cfc608aacfebb0#code) is pausable. There is a private list of addresses (stored in the "_pausers" private role) that can unilaterally pause the entire MATIC token without needing any other members to approve. > > **Centralized control of Polygon contracts on Ethereum mainnet via its Multisig owner account** > > At any given time, Polygon can update its contracts using this Multisig Gnosis Safe, and it has already done so **40 times in the past year** and 170 times in the past 2 years. That's a lot of unannounced updates. > > It does this through a [5 out of 9 Multisig Gnosis Safe](https://etherscan.io/address/0xfa7d2a996ac6350f4b56c043112da0366a59b74c) (often misquoted as an 5 out of 8 Multisig) that controls all of Polygon's contracts on Ethereum (e.g. Plasma Bridge, PoS Bridge, Staking Contract, Governance Proxy, Ether Bridge, Root Chain Proxy, Polygon-to-Ethereum token mapping, and many other contracts). 4 of these owners are Polygon members, 4 are external DeFi users, and 1 is an unknown account (possibly the owner of Quickswap). > > **[My own investigation](https://mplankton.substack.com/p/investigating-the-59-polygon-multisig) discovered that this MultiSig account is one of the worst-documented parts of Polygon**: > > * Every media site, blog, and forum to this day still thinks it's an 5/8 Multisig based on an old letter back in May 2021. The fact that no one has mentioned the 9th owner (added 2 years ago) is a strong sign the public isn't actually auditing the Polygon admin actions on that Multisig contract. > * A 9th owner was added back [in June 2021](https://etherscan.io/tx/0xb02b91300e3cea5bb788513cd858f27f27410b3bc67b8e12dca10944b4d611c8) **unannounced**. An additional 2 Polygon owners were swapped in the past year **unannounced**. > * [Back in Aug 2021](https://etherscan.io/tx/0x9eca1e21c66d7a30bfb69dedb0857314cf7ed127d149328d518678f7e22fbdb9), ownership of all Polygon's contracts were replaced by a [TimeLock contract](https://etherscan.io/address/0xCaf0aa768A3AE1297DF20072419Db8Bb8b5C8cEf). This Timelock provides an acceptance window where any action on Polygon's contracts has to wait 48 hours before it takes effect. The Timelock is in turn controlled by the 5/9 Gnosis Safe account. > * Polygon's websites, forums, Discord channel, and subreddit don't mention the Timelock. > * **Even Polygon's own documentation team is unaware of the Timelock.** There is [one document that mentions the Multisig address](https://wiki.polygon.technology/docs/faq/commit-chain-multisigs/) suggests that a Timelock is a future update, when it's actually already active. > > ####**Upgrade process is centralized** > > Polygon Labs controls the upgrade process through centralized governance. > > Back in Dec 2021, the Polygon team [secretly hard-forked the network](https://cryptobriefing.com/a-hacker-stole-1-6m-after-exploiting-a-polygon-bug/) by pushing out a patch 1 day after a hacker stole $1.6M from the network from the Polygon PoS genesis contract in Dec 2021. The team didn't publicize the reason for the emergency patch until over 3 weeks later. > > In Jan 2023, the **Delhi Hardfork, PIP-7**, was voted on by only [15 out of 100 non-dev validators](https://forum.polygon.technology/t/pre-pip-discussion-addressing-reorgs-and-gas-spikes/10623). The vote was only used as non-binding feedback, so Polygon Lab devs still maintained real control over the upgrade. > > In Feb 2023, there was a client bug that caused [a multi-validator outage and 153-block reorg](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/). Due to the outage and slow syncing where many out-of-sync validators were taking up to a day to resync, many of them were missing their 98% checkpoint SLA requirements for staying on as a validator. As a result, the Polygon team pushed **an emergency proposal, PIP-9**, to reduce the threshold back to 95%. In less than half a day, it passed and was activated. Even over 4 days, only 27 out of 100 validators had voted on it. > > **Future decentralized governance** > > It's been over a year since Polygon posted they were looking into [Governance Decentralization](https://blog.polygon.technology/state-of-governance-decentralization/). It wasn't until only Feb 2023 that they started the first steps towards decentralized governance via [PIP-1](https://forum.pol... ***** Would you like to learn more? Check out the [Cointest archive](/r/CointestOfficial/wiki/cointest_archive#wiki_Polygon) to find submissions for other topics.

CointestMod

#Polygon Con-Arguments Below is a Polygon con-argument written by a deleted user. > ####**Has plenty of competitors, including itself** > > Currently, Polygon PoS is competing against optimistic L2 blockchains like Arbitrum One and Optimism. Arbitrum has nearly [2x the TVL as Polygon](https://defillama.com/chains), and Optimism has almost caught up. > > Polygon's future zkEVM rollup is also competing against other zkEVM rollups. Once its zkEVM is released, it's possible it's going to split the Polygon community between those who want to stay on the sidechain and those who want to use the zkEVM. **If you look at their [zkEVM testnet](https://explorer.public.zkevm-test.net/txs?block_number=143530&index=0&page_number=1&page_size=50&pages_limit=200), fees are paid in Ether, not MATIC.** That's bearish for MATIC token utility. > > **TVL has dropped considerably compared to L2s** > > One year ago back in Jan 2022, [Polygon TVL was $4.8B USD](https://defillama.com/chain/Polygon) while the combined [Layer 2 rollup TVL was $5.4B USD](https://l2beat.com/scaling/tvl). While L2 TVL has increased a little despite the bear market, Polygon's TVL has collapsed by 75% to $1.2B. > > **Growing dApp competition from L2 rollups** > > A year ago, Polygon PoS was unique in that it was the only network besides Ethereum that had OpenSea support. Now OpenSea supports a dozen different networks, including competing Layer 2 rollups networks like Optimism, Arbitrum One, and even Arbitrum Nova. So there's a lot more competition. > > **Declining social media support** > > With L2 rollups developing so quickly, many in the Ethereum community have turned against Polygon, creating a narrative that it's "just a sidechain", not a true Layer 2. > > The 0xPolygon subreddit has become more of a ghost town with noticeable amounts of spam posts. I don't think its mods are checking regularly anymore. > > ####**Less resistant to DDoS attacks and spam** > > Like all networks with low transaction fees, it's at risk of DDoS attacks. > > In early Jan 2022, [Sunflowers Farm \(SFF\) unintentionally DDoS-attacked the Polygon PoS network](https://www.coindesk.com/tech/2022/01/06/polygon-under-accidental-attack-from-swarm-of-sunflower-farmers/) and completely congested the network because it was more profitable to play the game and spam transactions than pay network fees. Transaction fees shot up 20x. Eventually, a hacker exploited the SFF game and reduced its price to zero, and users rejoiced because it cleared the congestion. > > **It has a Gas Cartel** > > Spam attacks were eventually mitigated when the whole Polygon validator community chose to [lock priority fees at a 30 Gwei minimum](https://cryptoslate.com/polygon-matic-to-raise-gas-fee-to-30-gwei-to-prevent-spam-transactions/). That's not an offical part of protocol. Polygon validators have colluded off-chain and are running **gas cartel**, like OPEC. > > However, it still gets tons of spam transactions, which I have experienced first-hand many times. All my Polygon accounts with activity on them were randomly sent spam tokens and NFTs. Many of these tokens are part of scam that try to trick you into interacting with them by selling them. Other are advertising sketchy website links. > > This is the downside of having sub-penny transactions. > > ####**Still requires the Ethereum network** > > The Polygon PoS network is a side chain for Ethereum. Many parts of Polygon still require Ethereum and pay fees in ETH instead of MATIC. OpenSea's NFT are usually quoted in ETH instead of MATIC. The MATIC token its originates on Ethereum and is bridged over to Polygon PoS as an ERC-20 token. Staking is also done on the Ethereum mainnet. The periodic Polygon checkpoints require paying Ethereum fees too. > > Thus Polygon's success depends on Ethereum's success and security. > > Going from Layer 1 Ethereum to Polygon is mainly done through the Polygon PoS bridge, which costs Ethereum gas fees. The first time bridging over to Polygon can be stressful. Their documentation says it should only take [22-30 minutes](https://wiki.polygon.technology/docs/develop/ethereum-polygon/getting-started/) when it often takes many hours as many people including me have found out the hard way. > > ####**Numerous reorgs** > > Polygon has [multiple reorgs every day](https://polygonscan.com/blocks_forked). Many of these are of 10+ depths, which is dangerously high. Due to reorgs, transactions up to 32 blocks ago can be completely reversed. In fact, up until the Delhi update (Jan 17, 2023), it was common to see reorgs up to 128-blocks ago (5 minutes). After the update, this has been reduced to a max of 32 blocks (1 minute). That's better than before the update, but it's still a lot. The reason behind this unique and dangerous Polygon phenomenon is due to the validator sprints that it uses on the Bor block production layer. [I wrote a separate article to explain this phenomenon](https://mplankton.substack.com/p/polygons-block-reorg-problem). > > Even after the Delhi update, there was still a massive [153-block reorg in Feb 2023](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/) and multiple-validator outage caused by an unrelated bug. > > ####**Centralization concerns** > > **Pausable tokens** > > The [MATIC token contract](https://etherscan.io/token/0x7d1afa7b718fb893db30a3abc0cfc608aacfebb0#code) is pausable. There is a private list of addresses (stored in the "_pausers" private role) that can unilaterally pause the entire MATIC token without needing any other members to approve. > > **Centralized control of Polygon contracts on Ethereum mainnet via its Multisig owner account** > > At any given time, Polygon can update its contracts using this Multisig Gnosis Safe, and it has already done so **40 times in the past year** and 170 times in the past 2 years. That's a lot of unannounced updates. > > It does this through a [5 out of 9 Multisig Gnosis Safe](https://etherscan.io/address/0xfa7d2a996ac6350f4b56c043112da0366a59b74c) (often misquoted as an 5 out of 8 Multisig) that controls all of Polygon's contracts on Ethereum (e.g. Plasma Bridge, PoS Bridge, Staking Contract, Governance Proxy, Ether Bridge, Root Chain Proxy, Polygon-to-Ethereum token mapping, and many other contracts). 4 of these owners are Polygon members, 4 are external DeFi users, and 1 is an unknown account (possibly the owner of Quickswap). > > **[My own investigation](https://mplankton.substack.com/p/investigating-the-59-polygon-multisig) discovered that this MultiSig account is one of the worst-documented parts of Polygon**: > > * Every media site, blog, and forum to this day still thinks it's an 5/8 Multisig based on an old letter back in May 2021. The fact that no one has mentioned the 9th owner (added 2 years ago) is a strong sign the public isn't actually auditing the Polygon admin actions on that Multisig contract. > * A 9th owner was added back [in June 2021](https://etherscan.io/tx/0xb02b91300e3cea5bb788513cd858f27f27410b3bc67b8e12dca10944b4d611c8) **unannounced**. An additional 2 Polygon owners were swapped in the past year **unannounced**. > * [Back in Aug 2021](https://etherscan.io/tx/0x9eca1e21c66d7a30bfb69dedb0857314cf7ed127d149328d518678f7e22fbdb9), ownership of all Polygon's contracts were replaced by a [TimeLock contract](https://etherscan.io/address/0xCaf0aa768A3AE1297DF20072419Db8Bb8b5C8cEf). This Timelock provides an acceptance window where any action on Polygon's contracts has to wait 48 hours before it takes effect. The Timelock is in turn controlled by the 5/9 Gnosis Safe account. > * Polygon's websites, forums, Discord channel, and subreddit don't mention the Timelock. > * **Even Polygon's own documentation team is unaware of the Timelock.** There is [one document that mentions the Multisig address](https://wiki.polygon.technology/docs/faq/commit-chain-multisigs/) suggests that a Timelock is a future update, when it's actually already active. > > ####**Upgrade process is centralized** > > Polygon Labs controls the upgrade process through centralized governance. > > Back in Dec 2021, the Polygon team [secretly hard-forked the network](https://cryptobriefing.com/a-hacker-stole-1-6m-after-exploiting-a-polygon-bug/) by pushing out a patch 1 day after a hacker stole $1.6M from the network from the Polygon PoS genesis contract in Dec 2021. The team didn't publicize the reason for the emergency patch until over 3 weeks later. > > In Jan 2023, the **Delhi Hardfork, PIP-7**, was voted on by only [15 out of 100 non-dev validators](https://forum.polygon.technology/t/pre-pip-discussion-addressing-reorgs-and-gas-spikes/10623). The vote was only used as non-binding feedback, so Polygon Lab devs still maintained real control over the upgrade. > > In Feb 2023, there was a client bug that caused [a multi-validator outage and 153-block reorg](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/). Due to the outage and slow syncing where many out-of-sync validators were taking up to a day to resync, many of them were missing their 98% checkpoint SLA requirements for staying on as a validator. As a result, the Polygon team pushed **an emergency proposal, PIP-9**, to reduce the threshold back to 95%. In less than half a day, it passed and was activated. Even over 4 days, only 27 out of 100 validators had voted on it. > > **Future decentralized governance** > > It's been over a year since Polygon posted they were looking into [Governance Decentralization](https://blog.polygon.technology/state-of-governance-decentralization/). It wasn't until only Feb 2023 that they started the first steps towards decentralized governance via [PIP-1](https://forum.pol... ***** Would you like to learn more? Check out the [Cointest archive](/r/CointestOfficial/wiki/cointest_archive#wiki_Polygon) to find submissions for other topics.

Adamantinian

Nano sent [successfully](https://nanolooker.com/block/69C76E07AA9F913887FAC49CFC11756AE5EB3593B7170A9736E06FDA3D6D3B62)! **Learn more about Nano** - Read [this article](https://senatus.substack.com/p/the-basics-of-nano-why-its-such-an) for the basics. - Visit [Nano.community](https://nano.community/introduction/basics) for comprehensive information. **Try a faucet** - [NanoDrop](https://nanodrop.io/) sends some Nano instantly. - [WeNano](https://wenano.net/) has location-based faucets all over the world. **Use Nano** - Queue videos for others to watch or get paid to watch on [CryptoVision](https://cryptovision.live/). - Pay per prompt to access ChatGPT4, DALL·E 3 and more via [Nano-GPT](https://nano-gpt.com/). - Easily develop with Nano using a [Public Node](https://rpc.nano.to) (we're using one right now). **Ask questions** - If you have any further questions, come on over to r/nanocurrency! **Random Nano fact**: Nano's node software is written in C++, but a developer is [currently also porting it to Rust](https://www.rsnano.com/). He does coding livestreams where you can follow along!

Adamantinian

Nano sent [successfully](https://nanolooker.com/block/DE6801EAC84AE4D6DD178386E415334CAC898EA040B57BEBEA4B44D26F1CDDA2)! **Learn more about Nano** - Read [this article](https://senatus.substack.com/p/the-basics-of-nano-why-its-such-an) for the basics. - Visit [Nano.community](https://nano.community/introduction/basics) for comprehensive information. **Try a faucet** - [NanoDrop](https://nanodrop.io/) sends some Nano instantly. - [WeNano](https://wenano.net/) has location-based faucets all over the world. **Use Nano** - Queue videos for others to watch or get paid to watch on [CryptoVision](https://cryptovision.live/). - Pay per prompt to access ChatGPT4, DALL·E 3 and more via [Nano-GPT](https://nano-gpt.com/). - Easily develop with Nano using a [Public Node](https://rpc.nano.to) (we're using one right now). **Ask questions** - If you have any further questions, come on over to r/nanocurrency! **Random Nano fact**: It's recently become possible to add the Nano Ӿ symbol (its currency symbol) into [AI generated images](https://nano.org/en/blog/how-to-add-nano-currency-symbol-ai-image-generations--267803bb)!

Adamantinian

Nano sent [successfully](https://nanolooker.com/block/CB05438F520D16606AE1C1C71C303A2FB465BEEA5F80D641FBF7FE61B64DC314)! **Learn more about Nano** - Read [this article](https://senatus.substack.com/p/the-basics-of-nano-why-its-such-an) for the basics. - Visit [Nano.community](https://nano.community/introduction/basics) for comprehensive information. **Try a faucet** - [NanoDrop](https://nanodrop.io/) sends some Nano instantly. - [WeNano](https://wenano.net/) has location-based faucets all over the world. **Use Nano** - Queue videos for others to watch or get paid to watch on [CryptoVision](https://cryptovision.live/). - Pay per prompt to access ChatGPT4, DALL·E 3 and more via [Nano-GPT](https://nano-gpt.com/). - Easily develop with Nano using a [Public Node](https://rpc.nano.to) (we're using one right now). **Ask questions** - If you have any further questions, come on over to r/nanocurrency! **Random Nano fact**: Nano has been flying with the International Space Station on a WeNano spot. People can collect small amounts of Nano when the ISS overflies their location!

Adamantinian

Nano sent [successfully](https://nanolooker.com/block/4B51BACD2273B229EEED889C045EC12EF1F58AE0505DA0F4AA4DA02026F5B678)! **Learn more about Nano** - Read [this article](https://senatus.substack.com/p/the-basics-of-nano-why-its-such-an) for the basics. - Visit [Nano.community](https://nano.community/introduction/basics) for comprehensive information. **Try a faucet** - [NanoDrop](https://nanodrop.io/) sends some Nano instantly. - [WeNano](https://wenano.net/) has location-based faucets all over the world. **Use Nano** - Queue videos for others to watch or get paid to watch on [CryptoVision](https://cryptovision.live/). - Pay per prompt to access ChatGPT4, DALL·E 3 and more via [Nano-GPT](https://nano-gpt.com/). - Easily develop with Nano using a [Public Node](https://rpc.nano.to) (we're using one right now). **Ask questions** - If you have any further questions, come on over to r/nanocurrency! **Random Nano fact**: Nano has no inbuilt limits. Its throughput is dependent on the hardware and bandwidth of the nodes running the network. If they get stronger, the network's throughput increases.

CointestMod

#Polygon Con-Arguments Below is a Polygon con-argument written by a deleted user. > ####**Has plenty of competitors, including itself** > > Currently, Polygon PoS is competing against optimistic L2 blockchains like Arbitrum One and Optimism. Arbitrum has nearly [2x the TVL as Polygon](https://defillama.com/chains), and Optimism has almost caught up. > > Polygon's future zkEVM rollup is also competing against other zkEVM rollups. Once its zkEVM is released, it's possible it's going to split the Polygon community between those who want to stay on the sidechain and those who want to use the zkEVM. **If you look at their [zkEVM testnet](https://explorer.public.zkevm-test.net/txs?block_number=143530&index=0&page_number=1&page_size=50&pages_limit=200), fees are paid in Ether, not MATIC.** That's bearish for MATIC token utility. > > **TVL has dropped considerably compared to L2s** > > One year ago back in Jan 2022, [Polygon TVL was $4.8B USD](https://defillama.com/chain/Polygon) while the combined [Layer 2 rollup TVL was $5.4B USD](https://l2beat.com/scaling/tvl). While L2 TVL has increased a little despite the bear market, Polygon's TVL has collapsed by 75% to $1.2B. > > **Growing dApp competition from L2 rollups** > > A year ago, Polygon PoS was unique in that it was the only network besides Ethereum that had OpenSea support. Now OpenSea supports a dozen different networks, including competing Layer 2 rollups networks like Optimism, Arbitrum One, and even Arbitrum Nova. So there's a lot more competition. > > **Declining social media support** > > With L2 rollups developing so quickly, many in the Ethereum community have turned against Polygon, creating a narrative that it's "just a sidechain", not a true Layer 2. > > The 0xPolygon subreddit has become more of a ghost town with noticeable amounts of spam posts. I don't think its mods are checking regularly anymore. > > ####**Less resistant to DDoS attacks and spam** > > Like all networks with low transaction fees, it's at risk of DDoS attacks. > > In early Jan 2022, [Sunflowers Farm \(SFF\) unintentionally DDoS-attacked the Polygon PoS network](https://www.coindesk.com/tech/2022/01/06/polygon-under-accidental-attack-from-swarm-of-sunflower-farmers/) and completely congested the network because it was more profitable to play the game and spam transactions than pay network fees. Transaction fees shot up 20x. Eventually, a hacker exploited the SFF game and reduced its price to zero, and users rejoiced because it cleared the congestion. > > **It has a Gas Cartel** > > Spam attacks were eventually mitigated when the whole Polygon validator community chose to [lock priority fees at a 30 Gwei minimum](https://cryptoslate.com/polygon-matic-to-raise-gas-fee-to-30-gwei-to-prevent-spam-transactions/). That's not an offical part of protocol. Polygon validators have colluded off-chain and are running **gas cartel**, like OPEC. > > However, it still gets tons of spam transactions, which I have experienced first-hand many times. All my Polygon accounts with activity on them were randomly sent spam tokens and NFTs. Many of these tokens are part of scam that try to trick you into interacting with them by selling them. Other are advertising sketchy website links. > > This is the downside of having sub-penny transactions. > > ####**Still requires the Ethereum network** > > The Polygon PoS network is a side chain for Ethereum. Many parts of Polygon still require Ethereum and pay fees in ETH instead of MATIC. OpenSea's NFT are usually quoted in ETH instead of MATIC. The MATIC token its originates on Ethereum and is bridged over to Polygon PoS as an ERC-20 token. Staking is also done on the Ethereum mainnet. The periodic Polygon checkpoints require paying Ethereum fees too. > > Thus Polygon's success depends on Ethereum's success and security. > > Going from Layer 1 Ethereum to Polygon is mainly done through the Polygon PoS bridge, which costs Ethereum gas fees. The first time bridging over to Polygon can be stressful. Their documentation says it should only take [22-30 minutes](https://wiki.polygon.technology/docs/develop/ethereum-polygon/getting-started/) when it often takes many hours as many people including me have found out the hard way. > > ####**Numerous reorgs** > > Polygon has [multiple reorgs every day](https://polygonscan.com/blocks_forked). Many of these are of 10+ depths, which is dangerously high. Due to reorgs, transactions up to 32 blocks ago can be completely reversed. In fact, up until the Delhi update (Jan 17, 2023), it was common to see reorgs up to 128-blocks ago (5 minutes). After the update, this has been reduced to a max of 32 blocks (1 minute). That's better than before the update, but it's still a lot. The reason behind this unique and dangerous Polygon phenomenon is due to the validator sprints that it uses on the Bor block production layer. [I wrote a separate article to explain this phenomenon](https://mplankton.substack.com/p/polygons-block-reorg-problem). > > Even after the Delhi update, there was still a massive [153-block reorg in Feb 2023](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/) and multiple-validator outage caused by an unrelated bug. > > ####**Centralization concerns** > > **Pausable tokens** > > The [MATIC token contract](https://etherscan.io/token/0x7d1afa7b718fb893db30a3abc0cfc608aacfebb0#code) is pausable. There is a private list of addresses (stored in the "_pausers" private role) that can unilaterally pause the entire MATIC token without needing any other members to approve. > > **Centralized control of Polygon contracts on Ethereum mainnet via its Multisig owner account** > > At any given time, Polygon can update its contracts using this Multisig Gnosis Safe, and it has already done so **40 times in the past year** and 170 times in the past 2 years. That's a lot of unannounced updates. > > It does this through a [5 out of 9 Multisig Gnosis Safe](https://etherscan.io/address/0xfa7d2a996ac6350f4b56c043112da0366a59b74c) (often misquoted as an 5 out of 8 Multisig) that controls all of Polygon's contracts on Ethereum (e.g. Plasma Bridge, PoS Bridge, Staking Contract, Governance Proxy, Ether Bridge, Root Chain Proxy, Polygon-to-Ethereum token mapping, and many other contracts). 4 of these owners are Polygon members, 4 are external DeFi users, and 1 is an unknown account (possibly the owner of Quickswap). > > **[My own investigation](https://mplankton.substack.com/p/investigating-the-59-polygon-multisig) discovered that this MultiSig account is one of the worst-documented parts of Polygon**: > > * Every media site, blog, and forum to this day still thinks it's an 5/8 Multisig based on an old letter back in May 2021. The fact that no one has mentioned the 9th owner (added 2 years ago) is a strong sign the public isn't actually auditing the Polygon admin actions on that Multisig contract. > * A 9th owner was added back [in June 2021](https://etherscan.io/tx/0xb02b91300e3cea5bb788513cd858f27f27410b3bc67b8e12dca10944b4d611c8) **unannounced**. An additional 2 Polygon owners were swapped in the past year **unannounced**. > * [Back in Aug 2021](https://etherscan.io/tx/0x9eca1e21c66d7a30bfb69dedb0857314cf7ed127d149328d518678f7e22fbdb9), ownership of all Polygon's contracts were replaced by a [TimeLock contract](https://etherscan.io/address/0xCaf0aa768A3AE1297DF20072419Db8Bb8b5C8cEf). This Timelock provides an acceptance window where any action on Polygon's contracts has to wait 48 hours before it takes effect. The Timelock is in turn controlled by the 5/9 Gnosis Safe account. > * Polygon's websites, forums, Discord channel, and subreddit don't mention the Timelock. > * **Even Polygon's own documentation team is unaware of the Timelock.** There is [one document that mentions the Multisig address](https://wiki.polygon.technology/docs/faq/commit-chain-multisigs/) suggests that a Timelock is a future update, when it's actually already active. > > ####**Upgrade process is centralized** > > Polygon Labs controls the upgrade process through centralized governance. > > Back in Dec 2021, the Polygon team [secretly hard-forked the network](https://cryptobriefing.com/a-hacker-stole-1-6m-after-exploiting-a-polygon-bug/) by pushing out a patch 1 day after a hacker stole $1.6M from the network from the Polygon PoS genesis contract in Dec 2021. The team didn't publicize the reason for the emergency patch until over 3 weeks later. > > In Jan 2023, the **Delhi Hardfork, PIP-7**, was voted on by only [15 out of 100 non-dev validators](https://forum.polygon.technology/t/pre-pip-discussion-addressing-reorgs-and-gas-spikes/10623). The vote was only used as non-binding feedback, so Polygon Lab devs still maintained real control over the upgrade. > > In Feb 2023, there was a client bug that caused [a multi-validator outage and 153-block reorg](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/). Due to the outage and slow syncing where many out-of-sync validators were taking up to a day to resync, many of them were missing their 98% checkpoint SLA requirements for staying on as a validator. As a result, the Polygon team pushed **an emergency proposal, PIP-9**, to reduce the threshold back to 95%. In less than half a day, it passed and was activated. Even over 4 days, only 27 out of 100 validators had voted on it. > > **Future decentralized governance** > > It's been over a year since Polygon posted they were looking into [Governance Decentralization](https://blog.polygon.technology/state-of-governance-decentralization/). It wasn't until only Feb 2023 that they started the first steps towards decentralized governance via [PIP-1](https://forum.pol... ***** Would you like to learn more? Check out the [Cointest archive](/r/CointestOfficial/wiki/cointest_archive#wiki_Polygon) to find submissions for other topics.

DackNBills878

"The main ideas come from the investing philosophy of Vanguard's founder, John Bogle." [https://www.bogleheads.org/wiki/Bogleheads%C2%AE\_investment\_philosophy](https://www.bogleheads.org/wiki/Bogleheads%C2%AE_investment_philosophy) I just searched it now though. I think that crowd is not ready to put much allocation in bitcoin. To each their own I suppose

sburke0708

No no, you send btc to your own wallet. I am doing a poor job of explaining. Watch a few minutes of this video and I’m sure you’ll see what I mean: https://youtu.be/yfbq0s5Y1AE?si=1i9tcISslbToee9V

CointestMod

#Polygon Con-Arguments Below is a Polygon con-argument written by a deleted user. > ####**Has plenty of competitors, including itself** > > Currently, Polygon PoS is competing against optimistic L2 blockchains like Arbitrum One and Optimism. Arbitrum has nearly [2x the TVL as Polygon](https://defillama.com/chains), and Optimism has almost caught up. > > Polygon's future zkEVM rollup is also competing against other zkEVM rollups. Once its zkEVM is released, it's possible it's going to split the Polygon community between those who want to stay on the sidechain and those who want to use the zkEVM. **If you look at their [zkEVM testnet](https://explorer.public.zkevm-test.net/txs?block_number=143530&index=0&page_number=1&page_size=50&pages_limit=200), fees are paid in Ether, not MATIC.** That's bearish for MATIC token utility. > > **TVL has dropped considerably compared to L2s** > > One year ago back in Jan 2022, [Polygon TVL was $4.8B USD](https://defillama.com/chain/Polygon) while the combined [Layer 2 rollup TVL was $5.4B USD](https://l2beat.com/scaling/tvl). While L2 TVL has increased a little despite the bear market, Polygon's TVL has collapsed by 75% to $1.2B. > > **Growing dApp competition from L2 rollups** > > A year ago, Polygon PoS was unique in that it was the only network besides Ethereum that had OpenSea support. Now OpenSea supports a dozen different networks, including competing Layer 2 rollups networks like Optimism, Arbitrum One, and even Arbitrum Nova. So there's a lot more competition. > > **Declining social media support** > > With L2 rollups developing so quickly, many in the Ethereum community have turned against Polygon, creating a narrative that it's "just a sidechain", not a true Layer 2. > > The 0xPolygon subreddit has become more of a ghost town with noticeable amounts of spam posts. I don't think its mods are checking regularly anymore. > > ####**Less resistant to DDoS attacks and spam** > > Like all networks with low transaction fees, it's at risk of DDoS attacks. > > In early Jan 2022, [Sunflowers Farm \(SFF\) unintentionally DDoS-attacked the Polygon PoS network](https://www.coindesk.com/tech/2022/01/06/polygon-under-accidental-attack-from-swarm-of-sunflower-farmers/) and completely congested the network because it was more profitable to play the game and spam transactions than pay network fees. Transaction fees shot up 20x. Eventually, a hacker exploited the SFF game and reduced its price to zero, and users rejoiced because it cleared the congestion. > > **It has a Gas Cartel** > > Spam attacks were eventually mitigated when the whole Polygon validator community chose to [lock priority fees at a 30 Gwei minimum](https://cryptoslate.com/polygon-matic-to-raise-gas-fee-to-30-gwei-to-prevent-spam-transactions/). That's not an offical part of protocol. Polygon validators have colluded off-chain and are running **gas cartel**, like OPEC. > > However, it still gets tons of spam transactions, which I have experienced first-hand many times. All my Polygon accounts with activity on them were randomly sent spam tokens and NFTs. Many of these tokens are part of scam that try to trick you into interacting with them by selling them. Other are advertising sketchy website links. > > This is the downside of having sub-penny transactions. > > ####**Still requires the Ethereum network** > > The Polygon PoS network is a side chain for Ethereum. Many parts of Polygon still require Ethereum and pay fees in ETH instead of MATIC. OpenSea's NFT are usually quoted in ETH instead of MATIC. The MATIC token its originates on Ethereum and is bridged over to Polygon PoS as an ERC-20 token. Staking is also done on the Ethereum mainnet. The periodic Polygon checkpoints require paying Ethereum fees too. > > Thus Polygon's success depends on Ethereum's success and security. > > Going from Layer 1 Ethereum to Polygon is mainly done through the Polygon PoS bridge, which costs Ethereum gas fees. The first time bridging over to Polygon can be stressful. Their documentation says it should only take [22-30 minutes](https://wiki.polygon.technology/docs/develop/ethereum-polygon/getting-started/) when it often takes many hours as many people including me have found out the hard way. > > ####**Numerous reorgs** > > Polygon has [multiple reorgs every day](https://polygonscan.com/blocks_forked). Many of these are of 10+ depths, which is dangerously high. Due to reorgs, transactions up to 32 blocks ago can be completely reversed. In fact, up until the Delhi update (Jan 17, 2023), it was common to see reorgs up to 128-blocks ago (5 minutes). After the update, this has been reduced to a max of 32 blocks (1 minute). That's better than before the update, but it's still a lot. The reason behind this unique and dangerous Polygon phenomenon is due to the validator sprints that it uses on the Bor block production layer. [I wrote a separate article to explain this phenomenon](https://mplankton.substack.com/p/polygons-block-reorg-problem). > > Even after the Delhi update, there was still a massive [153-block reorg in Feb 2023](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/) and multiple-validator outage caused by an unrelated bug. > > ####**Centralization concerns** > > **Pausable tokens** > > The [MATIC token contract](https://etherscan.io/token/0x7d1afa7b718fb893db30a3abc0cfc608aacfebb0#code) is pausable. There is a private list of addresses (stored in the "_pausers" private role) that can unilaterally pause the entire MATIC token without needing any other members to approve. > > **Centralized control of Polygon contracts on Ethereum mainnet via its Multisig owner account** > > At any given time, Polygon can update its contracts using this Multisig Gnosis Safe, and it has already done so **40 times in the past year** and 170 times in the past 2 years. That's a lot of unannounced updates. > > It does this through a [5 out of 9 Multisig Gnosis Safe](https://etherscan.io/address/0xfa7d2a996ac6350f4b56c043112da0366a59b74c) (often misquoted as an 5 out of 8 Multisig) that controls all of Polygon's contracts on Ethereum (e.g. Plasma Bridge, PoS Bridge, Staking Contract, Governance Proxy, Ether Bridge, Root Chain Proxy, Polygon-to-Ethereum token mapping, and many other contracts). 4 of these owners are Polygon members, 4 are external DeFi users, and 1 is an unknown account (possibly the owner of Quickswap). > > **[My own investigation](https://mplankton.substack.com/p/investigating-the-59-polygon-multisig) discovered that this MultiSig account is one of the worst-documented parts of Polygon**: > > * Every media site, blog, and forum to this day still thinks it's an 5/8 Multisig based on an old letter back in May 2021. The fact that no one has mentioned the 9th owner (added 2 years ago) is a strong sign the public isn't actually auditing the Polygon admin actions on that Multisig contract. > * A 9th owner was added back [in June 2021](https://etherscan.io/tx/0xb02b91300e3cea5bb788513cd858f27f27410b3bc67b8e12dca10944b4d611c8) **unannounced**. An additional 2 Polygon owners were swapped in the past year **unannounced**. > * [Back in Aug 2021](https://etherscan.io/tx/0x9eca1e21c66d7a30bfb69dedb0857314cf7ed127d149328d518678f7e22fbdb9), ownership of all Polygon's contracts were replaced by a [TimeLock contract](https://etherscan.io/address/0xCaf0aa768A3AE1297DF20072419Db8Bb8b5C8cEf). This Timelock provides an acceptance window where any action on Polygon's contracts has to wait 48 hours before it takes effect. The Timelock is in turn controlled by the 5/9 Gnosis Safe account. > * Polygon's websites, forums, Discord channel, and subreddit don't mention the Timelock. > * **Even Polygon's own documentation team is unaware of the Timelock.** There is [one document that mentions the Multisig address](https://wiki.polygon.technology/docs/faq/commit-chain-multisigs/) suggests that a Timelock is a future update, when it's actually already active. > > ####**Upgrade process is centralized** > > Polygon Labs controls the upgrade process through centralized governance. > > Back in Dec 2021, the Polygon team [secretly hard-forked the network](https://cryptobriefing.com/a-hacker-stole-1-6m-after-exploiting-a-polygon-bug/) by pushing out a patch 1 day after a hacker stole $1.6M from the network from the Polygon PoS genesis contract in Dec 2021. The team didn't publicize the reason for the emergency patch until over 3 weeks later. > > In Jan 2023, the **Delhi Hardfork, PIP-7**, was voted on by only [15 out of 100 non-dev validators](https://forum.polygon.technology/t/pre-pip-discussion-addressing-reorgs-and-gas-spikes/10623). The vote was only used as non-binding feedback, so Polygon Lab devs still maintained real control over the upgrade. > > In Feb 2023, there was a client bug that caused [a multi-validator outage and 153-block reorg](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/). Due to the outage and slow syncing where many out-of-sync validators were taking up to a day to resync, many of them were missing their 98% checkpoint SLA requirements for staying on as a validator. As a result, the Polygon team pushed **an emergency proposal, PIP-9**, to reduce the threshold back to 95%. In less than half a day, it passed and was activated. Even over 4 days, only 27 out of 100 validators had voted on it. > > **Future decentralized governance** > > It's been over a year since Polygon posted they were looking into [Governance Decentralization](https://blog.polygon.technology/state-of-governance-decentralization/). It wasn't until only Feb 2023 that they started the first steps towards decentralized governance via [PIP-1](https://forum.pol... ***** Would you like to learn more? Check out the [Cointest archive](/r/CointestOfficial/wiki/cointest_archive#wiki_Polygon) to find submissions for other topics.

CointestMod

#Polygon Con-Arguments Below is a Polygon con-argument written by a deleted user. > ####**Has plenty of competitors, including itself** > > Currently, Polygon PoS is competing against optimistic L2 blockchains like Arbitrum One and Optimism. Arbitrum has nearly [2x the TVL as Polygon](https://defillama.com/chains), and Optimism has almost caught up. > > Polygon's future zkEVM rollup is also competing against other zkEVM rollups. Once its zkEVM is released, it's possible it's going to split the Polygon community between those who want to stay on the sidechain and those who want to use the zkEVM. **If you look at their [zkEVM testnet](https://explorer.public.zkevm-test.net/txs?block_number=143530&index=0&page_number=1&page_size=50&pages_limit=200), fees are paid in Ether, not MATIC.** That's bearish for MATIC token utility. > > **TVL has dropped considerably compared to L2s** > > One year ago back in Jan 2022, [Polygon TVL was $4.8B USD](https://defillama.com/chain/Polygon) while the combined [Layer 2 rollup TVL was $5.4B USD](https://l2beat.com/scaling/tvl). While L2 TVL has increased a little despite the bear market, Polygon's TVL has collapsed by 75% to $1.2B. > > **Growing dApp competition from L2 rollups** > > A year ago, Polygon PoS was unique in that it was the only network besides Ethereum that had OpenSea support. Now OpenSea supports a dozen different networks, including competing Layer 2 rollups networks like Optimism, Arbitrum One, and even Arbitrum Nova. So there's a lot more competition. > > **Declining social media support** > > With L2 rollups developing so quickly, many in the Ethereum community have turned against Polygon, creating a narrative that it's "just a sidechain", not a true Layer 2. > > The 0xPolygon subreddit has become more of a ghost town with noticeable amounts of spam posts. I don't think its mods are checking regularly anymore. > > ####**Less resistant to DDoS attacks and spam** > > Like all networks with low transaction fees, it's at risk of DDoS attacks. > > In early Jan 2022, [Sunflowers Farm \(SFF\) unintentionally DDoS-attacked the Polygon PoS network](https://www.coindesk.com/tech/2022/01/06/polygon-under-accidental-attack-from-swarm-of-sunflower-farmers/) and completely congested the network because it was more profitable to play the game and spam transactions than pay network fees. Transaction fees shot up 20x. Eventually, a hacker exploited the SFF game and reduced its price to zero, and users rejoiced because it cleared the congestion. > > **It has a Gas Cartel** > > Spam attacks were eventually mitigated when the whole Polygon validator community chose to [lock priority fees at a 30 Gwei minimum](https://cryptoslate.com/polygon-matic-to-raise-gas-fee-to-30-gwei-to-prevent-spam-transactions/). That's not an offical part of protocol. Polygon validators have colluded off-chain and are running **gas cartel**, like OPEC. > > However, it still gets tons of spam transactions, which I have experienced first-hand many times. All my Polygon accounts with activity on them were randomly sent spam tokens and NFTs. Many of these tokens are part of scam that try to trick you into interacting with them by selling them. Other are advertising sketchy website links. > > This is the downside of having sub-penny transactions. > > ####**Still requires the Ethereum network** > > The Polygon PoS network is a side chain for Ethereum. Many parts of Polygon still require Ethereum and pay fees in ETH instead of MATIC. OpenSea's NFT are usually quoted in ETH instead of MATIC. The MATIC token its originates on Ethereum and is bridged over to Polygon PoS as an ERC-20 token. Staking is also done on the Ethereum mainnet. The periodic Polygon checkpoints require paying Ethereum fees too. > > Thus Polygon's success depends on Ethereum's success and security. > > Going from Layer 1 Ethereum to Polygon is mainly done through the Polygon PoS bridge, which costs Ethereum gas fees. The first time bridging over to Polygon can be stressful. Their documentation says it should only take [22-30 minutes](https://wiki.polygon.technology/docs/develop/ethereum-polygon/getting-started/) when it often takes many hours as many people including me have found out the hard way. > > ####**Numerous reorgs** > > Polygon has [multiple reorgs every day](https://polygonscan.com/blocks_forked). Many of these are of 10+ depths, which is dangerously high. Due to reorgs, transactions up to 32 blocks ago can be completely reversed. In fact, up until the Delhi update (Jan 17, 2023), it was common to see reorgs up to 128-blocks ago (5 minutes). After the update, this has been reduced to a max of 32 blocks (1 minute). That's better than before the update, but it's still a lot. The reason behind this unique and dangerous Polygon phenomenon is due to the validator sprints that it uses on the Bor block production layer. [I wrote a separate article to explain this phenomenon](https://mplankton.substack.com/p/polygons-block-reorg-problem). > > Even after the Delhi update, there was still a massive [153-block reorg in Feb 2023](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/) and multiple-validator outage caused by an unrelated bug. > > ####**Centralization concerns** > > **Pausable tokens** > > The [MATIC token contract](https://etherscan.io/token/0x7d1afa7b718fb893db30a3abc0cfc608aacfebb0#code) is pausable. There is a private list of addresses (stored in the "_pausers" private role) that can unilaterally pause the entire MATIC token without needing any other members to approve. > > **Centralized control of Polygon contracts on Ethereum mainnet via its Multisig owner account** > > At any given time, Polygon can update its contracts using this Multisig Gnosis Safe, and it has already done so **40 times in the past year** and 170 times in the past 2 years. That's a lot of unannounced updates. > > It does this through a [5 out of 9 Multisig Gnosis Safe](https://etherscan.io/address/0xfa7d2a996ac6350f4b56c043112da0366a59b74c) (often misquoted as an 5 out of 8 Multisig) that controls all of Polygon's contracts on Ethereum (e.g. Plasma Bridge, PoS Bridge, Staking Contract, Governance Proxy, Ether Bridge, Root Chain Proxy, Polygon-to-Ethereum token mapping, and many other contracts). 4 of these owners are Polygon members, 4 are external DeFi users, and 1 is an unknown account (possibly the owner of Quickswap). > > **[My own investigation](https://mplankton.substack.com/p/investigating-the-59-polygon-multisig) discovered that this MultiSig account is one of the worst-documented parts of Polygon**: > > * Every media site, blog, and forum to this day still thinks it's an 5/8 Multisig based on an old letter back in May 2021. The fact that no one has mentioned the 9th owner (added 2 years ago) is a strong sign the public isn't actually auditing the Polygon admin actions on that Multisig contract. > * A 9th owner was added back [in June 2021](https://etherscan.io/tx/0xb02b91300e3cea5bb788513cd858f27f27410b3bc67b8e12dca10944b4d611c8) **unannounced**. An additional 2 Polygon owners were swapped in the past year **unannounced**. > * [Back in Aug 2021](https://etherscan.io/tx/0x9eca1e21c66d7a30bfb69dedb0857314cf7ed127d149328d518678f7e22fbdb9), ownership of all Polygon's contracts were replaced by a [TimeLock contract](https://etherscan.io/address/0xCaf0aa768A3AE1297DF20072419Db8Bb8b5C8cEf). This Timelock provides an acceptance window where any action on Polygon's contracts has to wait 48 hours before it takes effect. The Timelock is in turn controlled by the 5/9 Gnosis Safe account. > * Polygon's websites, forums, Discord channel, and subreddit don't mention the Timelock. > * **Even Polygon's own documentation team is unaware of the Timelock.** There is [one document that mentions the Multisig address](https://wiki.polygon.technology/docs/faq/commit-chain-multisigs/) suggests that a Timelock is a future update, when it's actually already active. > > ####**Upgrade process is centralized** > > Polygon Labs controls the upgrade process through centralized governance. > > Back in Dec 2021, the Polygon team [secretly hard-forked the network](https://cryptobriefing.com/a-hacker-stole-1-6m-after-exploiting-a-polygon-bug/) by pushing out a patch 1 day after a hacker stole $1.6M from the network from the Polygon PoS genesis contract in Dec 2021. The team didn't publicize the reason for the emergency patch until over 3 weeks later. > > In Jan 2023, the **Delhi Hardfork, PIP-7**, was voted on by only [15 out of 100 non-dev validators](https://forum.polygon.technology/t/pre-pip-discussion-addressing-reorgs-and-gas-spikes/10623). The vote was only used as non-binding feedback, so Polygon Lab devs still maintained real control over the upgrade. > > In Feb 2023, there was a client bug that caused [a multi-validator outage and 153-block reorg](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/). Due to the outage and slow syncing where many out-of-sync validators were taking up to a day to resync, many of them were missing their 98% checkpoint SLA requirements for staying on as a validator. As a result, the Polygon team pushed **an emergency proposal, PIP-9**, to reduce the threshold back to 95%. In less than half a day, it passed and was activated. Even over 4 days, only 27 out of 100 validators had voted on it. > > **Future decentralized governance** > > It's been over a year since Polygon posted they were looking into [Governance Decentralization](https://blog.polygon.technology/state-of-governance-decentralization/). It wasn't until only Feb 2023 that they started the first steps towards decentralized governance via [PIP-1](https://forum.pol... ***** Would you like to learn more? Check out the [Cointest archive](/r/CointestOfficial/wiki/cointest_archive#wiki_Polygon) to find submissions for other topics.

CointestMod

#Polygon Con-Arguments Below is a Polygon con-argument written by a deleted user. > ####**Has plenty of competitors, including itself** > > Currently, Polygon PoS is competing against optimistic L2 blockchains like Arbitrum One and Optimism. Arbitrum has nearly [2x the TVL as Polygon](https://defillama.com/chains), and Optimism has almost caught up. > > Polygon's future zkEVM rollup is also competing against other zkEVM rollups. Once its zkEVM is released, it's possible it's going to split the Polygon community between those who want to stay on the sidechain and those who want to use the zkEVM. **If you look at their [zkEVM testnet](https://explorer.public.zkevm-test.net/txs?block_number=143530&index=0&page_number=1&page_size=50&pages_limit=200), fees are paid in Ether, not MATIC.** That's bearish for MATIC token utility. > > **TVL has dropped considerably compared to L2s** > > One year ago back in Jan 2022, [Polygon TVL was $4.8B USD](https://defillama.com/chain/Polygon) while the combined [Layer 2 rollup TVL was $5.4B USD](https://l2beat.com/scaling/tvl). While L2 TVL has increased a little despite the bear market, Polygon's TVL has collapsed by 75% to $1.2B. > > **Growing dApp competition from L2 rollups** > > A year ago, Polygon PoS was unique in that it was the only network besides Ethereum that had OpenSea support. Now OpenSea supports a dozen different networks, including competing Layer 2 rollups networks like Optimism, Arbitrum One, and even Arbitrum Nova. So there's a lot more competition. > > **Declining social media support** > > With L2 rollups developing so quickly, many in the Ethereum community have turned against Polygon, creating a narrative that it's "just a sidechain", not a true Layer 2. > > The 0xPolygon subreddit has become more of a ghost town with noticeable amounts of spam posts. I don't think its mods are checking regularly anymore. > > ####**Less resistant to DDoS attacks and spam** > > Like all networks with low transaction fees, it's at risk of DDoS attacks. > > In early Jan 2022, [Sunflowers Farm \(SFF\) unintentionally DDoS-attacked the Polygon PoS network](https://www.coindesk.com/tech/2022/01/06/polygon-under-accidental-attack-from-swarm-of-sunflower-farmers/) and completely congested the network because it was more profitable to play the game and spam transactions than pay network fees. Transaction fees shot up 20x. Eventually, a hacker exploited the SFF game and reduced its price to zero, and users rejoiced because it cleared the congestion. > > **It has a Gas Cartel** > > Spam attacks were eventually mitigated when the whole Polygon validator community chose to [lock priority fees at a 30 Gwei minimum](https://cryptoslate.com/polygon-matic-to-raise-gas-fee-to-30-gwei-to-prevent-spam-transactions/). That's not an offical part of protocol. Polygon validators have colluded off-chain and are running **gas cartel**, like OPEC. > > However, it still gets tons of spam transactions, which I have experienced first-hand many times. All my Polygon accounts with activity on them were randomly sent spam tokens and NFTs. Many of these tokens are part of scam that try to trick you into interacting with them by selling them. Other are advertising sketchy website links. > > This is the downside of having sub-penny transactions. > > ####**Still requires the Ethereum network** > > The Polygon PoS network is a side chain for Ethereum. Many parts of Polygon still require Ethereum and pay fees in ETH instead of MATIC. OpenSea's NFT are usually quoted in ETH instead of MATIC. The MATIC token its originates on Ethereum and is bridged over to Polygon PoS as an ERC-20 token. Staking is also done on the Ethereum mainnet. The periodic Polygon checkpoints require paying Ethereum fees too. > > Thus Polygon's success depends on Ethereum's success and security. > > Going from Layer 1 Ethereum to Polygon is mainly done through the Polygon PoS bridge, which costs Ethereum gas fees. The first time bridging over to Polygon can be stressful. Their documentation says it should only take [22-30 minutes](https://wiki.polygon.technology/docs/develop/ethereum-polygon/getting-started/) when it often takes many hours as many people including me have found out the hard way. > > ####**Numerous reorgs** > > Polygon has [multiple reorgs every day](https://polygonscan.com/blocks_forked). Many of these are of 10+ depths, which is dangerously high. Due to reorgs, transactions up to 32 blocks ago can be completely reversed. In fact, up until the Delhi update (Jan 17, 2023), it was common to see reorgs up to 128-blocks ago (5 minutes). After the update, this has been reduced to a max of 32 blocks (1 minute). That's better than before the update, but it's still a lot. The reason behind this unique and dangerous Polygon phenomenon is due to the validator sprints that it uses on the Bor block production layer. [I wrote a separate article to explain this phenomenon](https://mplankton.substack.com/p/polygons-block-reorg-problem). > > Even after the Delhi update, there was still a massive [153-block reorg in Feb 2023](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/) and multiple-validator outage caused by an unrelated bug. > > ####**Centralization concerns** > > **Pausable tokens** > > The [MATIC token contract](https://etherscan.io/token/0x7d1afa7b718fb893db30a3abc0cfc608aacfebb0#code) is pausable. There is a private list of addresses (stored in the "_pausers" private role) that can unilaterally pause the entire MATIC token without needing any other members to approve. > > **Centralized control of Polygon contracts on Ethereum mainnet via its Multisig owner account** > > At any given time, Polygon can update its contracts using this Multisig Gnosis Safe, and it has already done so **40 times in the past year** and 170 times in the past 2 years. That's a lot of unannounced updates. > > It does this through a [5 out of 9 Multisig Gnosis Safe](https://etherscan.io/address/0xfa7d2a996ac6350f4b56c043112da0366a59b74c) (often misquoted as an 5 out of 8 Multisig) that controls all of Polygon's contracts on Ethereum (e.g. Plasma Bridge, PoS Bridge, Staking Contract, Governance Proxy, Ether Bridge, Root Chain Proxy, Polygon-to-Ethereum token mapping, and many other contracts). 4 of these owners are Polygon members, 4 are external DeFi users, and 1 is an unknown account (possibly the owner of Quickswap). > > **[My own investigation](https://mplankton.substack.com/p/investigating-the-59-polygon-multisig) discovered that this MultiSig account is one of the worst-documented parts of Polygon**: > > * Every media site, blog, and forum to this day still thinks it's an 5/8 Multisig based on an old letter back in May 2021. The fact that no one has mentioned the 9th owner (added 2 years ago) is a strong sign the public isn't actually auditing the Polygon admin actions on that Multisig contract. > * A 9th owner was added back [in June 2021](https://etherscan.io/tx/0xb02b91300e3cea5bb788513cd858f27f27410b3bc67b8e12dca10944b4d611c8) **unannounced**. An additional 2 Polygon owners were swapped in the past year **unannounced**. > * [Back in Aug 2021](https://etherscan.io/tx/0x9eca1e21c66d7a30bfb69dedb0857314cf7ed127d149328d518678f7e22fbdb9), ownership of all Polygon's contracts were replaced by a [TimeLock contract](https://etherscan.io/address/0xCaf0aa768A3AE1297DF20072419Db8Bb8b5C8cEf). This Timelock provides an acceptance window where any action on Polygon's contracts has to wait 48 hours before it takes effect. The Timelock is in turn controlled by the 5/9 Gnosis Safe account. > * Polygon's websites, forums, Discord channel, and subreddit don't mention the Timelock. > * **Even Polygon's own documentation team is unaware of the Timelock.** There is [one document that mentions the Multisig address](https://wiki.polygon.technology/docs/faq/commit-chain-multisigs/) suggests that a Timelock is a future update, when it's actually already active. > > ####**Upgrade process is centralized** > > Polygon Labs controls the upgrade process through centralized governance. > > Back in Dec 2021, the Polygon team [secretly hard-forked the network](https://cryptobriefing.com/a-hacker-stole-1-6m-after-exploiting-a-polygon-bug/) by pushing out a patch 1 day after a hacker stole $1.6M from the network from the Polygon PoS genesis contract in Dec 2021. The team didn't publicize the reason for the emergency patch until over 3 weeks later. > > In Jan 2023, the **Delhi Hardfork, PIP-7**, was voted on by only [15 out of 100 non-dev validators](https://forum.polygon.technology/t/pre-pip-discussion-addressing-reorgs-and-gas-spikes/10623). The vote was only used as non-binding feedback, so Polygon Lab devs still maintained real control over the upgrade. > > In Feb 2023, there was a client bug that caused [a multi-validator outage and 153-block reorg](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/). Due to the outage and slow syncing where many out-of-sync validators were taking up to a day to resync, many of them were missing their 98% checkpoint SLA requirements for staying on as a validator. As a result, the Polygon team pushed **an emergency proposal, PIP-9**, to reduce the threshold back to 95%. In less than half a day, it passed and was activated. Even over 4 days, only 27 out of 100 validators had voted on it. > > **Future decentralized governance** > > It's been over a year since Polygon posted they were looking into [Governance Decentralization](https://blog.polygon.technology/state-of-governance-decentralization/). It wasn't until only Feb 2023 that they started the first steps towards decentralized governance via [PIP-1](https://forum.pol... ***** Would you like to learn more? Check out the [Cointest archive](/r/CointestOfficial/wiki/cointest_archive#wiki_Polygon) to find submissions for other topics.

bobbyv137

When it broke $20k for the first time in last year’s bear market (a significant milestone number), there were threads on there such as “HERE AE GO BOYS!!”, with comments such as “opening the champagne as we speak!”. I may be paraphrasing but you get the gist. All Bitcoin did was retrace by a typical percentage draw down range as with previous bear markets. And as we all know, it’s now 100% up off the low. I never checked at the time, but I did wonder what they thought when the BlackRock ETF news broke. I guess the *experts* on that sub know better than BlackRock and the $9 trillion they manage.

SmoothGoing

Pub keys are not extremely long. They are a relatively short string not pages and pages of bits. Compressed pub key 0375CCD4CF547D08AB375AB2B798032921AE5C498C59C57FC47A89CA73CA148DCE Address is created by hashing pub key with 2 different algos a few times, adding a checksum and version byte, and encoding in base58 or bech32 format.

CointestMod

#Polygon Con-Arguments Below is a Polygon con-argument written by a deleted user. > ####**Has plenty of competitors, including itself** > > Currently, Polygon PoS is competing against optimistic L2 blockchains like Arbitrum One and Optimism. Arbitrum has nearly [2x the TVL as Polygon](https://defillama.com/chains), and Optimism has almost caught up. > > Polygon's future zkEVM rollup is also competing against other zkEVM rollups. Once its zkEVM is released, it's possible it's going to split the Polygon community between those who want to stay on the sidechain and those who want to use the zkEVM. **If you look at their [zkEVM testnet](https://explorer.public.zkevm-test.net/txs?block_number=143530&index=0&page_number=1&page_size=50&pages_limit=200), fees are paid in Ether, not MATIC.** That's bearish for MATIC token utility. > > **TVL has dropped considerably compared to L2s** > > One year ago back in Jan 2022, [Polygon TVL was $4.8B USD](https://defillama.com/chain/Polygon) while the combined [Layer 2 rollup TVL was $5.4B USD](https://l2beat.com/scaling/tvl). While L2 TVL has increased a little despite the bear market, Polygon's TVL has collapsed by 75% to $1.2B. > > **Growing dApp competition from L2 rollups** > > A year ago, Polygon PoS was unique in that it was the only network besides Ethereum that had OpenSea support. Now OpenSea supports a dozen different networks, including competing Layer 2 rollups networks like Optimism, Arbitrum One, and even Arbitrum Nova. So there's a lot more competition. > > **Declining social media support** > > With L2 rollups developing so quickly, many in the Ethereum community have turned against Polygon, creating a narrative that it's "just a sidechain", not a true Layer 2. > > The 0xPolygon subreddit has become more of a ghost town with noticeable amounts of spam posts. I don't think its mods are checking regularly anymore. > > ####**Less resistant to DDoS attacks and spam** > > Like all networks with low transaction fees, it's at risk of DDoS attacks. > > In early Jan 2022, [Sunflowers Farm \(SFF\) unintentionally DDoS-attacked the Polygon PoS network](https://www.coindesk.com/tech/2022/01/06/polygon-under-accidental-attack-from-swarm-of-sunflower-farmers/) and completely congested the network because it was more profitable to play the game and spam transactions than pay network fees. Transaction fees shot up 20x. Eventually, a hacker exploited the SFF game and reduced its price to zero, and users rejoiced because it cleared the congestion. > > **It has a Gas Cartel** > > Spam attacks were eventually mitigated when the whole Polygon validator community chose to [lock priority fees at a 30 Gwei minimum](https://cryptoslate.com/polygon-matic-to-raise-gas-fee-to-30-gwei-to-prevent-spam-transactions/). That's not an offical part of protocol. Polygon validators have colluded off-chain and are running **gas cartel**, like OPEC. > > However, it still gets tons of spam transactions, which I have experienced first-hand many times. All my Polygon accounts with activity on them were randomly sent spam tokens and NFTs. Many of these tokens are part of scam that try to trick you into interacting with them by selling them. Other are advertising sketchy website links. > > This is the downside of having sub-penny transactions. > > ####**Still requires the Ethereum network** > > The Polygon PoS network is a side chain for Ethereum. Many parts of Polygon still require Ethereum and pay fees in ETH instead of MATIC. OpenSea's NFT are usually quoted in ETH instead of MATIC. The MATIC token its originates on Ethereum and is bridged over to Polygon PoS as an ERC-20 token. Staking is also done on the Ethereum mainnet. The periodic Polygon checkpoints require paying Ethereum fees too. > > Thus Polygon's success depends on Ethereum's success and security. > > Going from Layer 1 Ethereum to Polygon is mainly done through the Polygon PoS bridge, which costs Ethereum gas fees. The first time bridging over to Polygon can be stressful. Their documentation says it should only take [22-30 minutes](https://wiki.polygon.technology/docs/develop/ethereum-polygon/getting-started/) when it often takes many hours as many people including me have found out the hard way. > > ####**Numerous reorgs** > > Polygon has [multiple reorgs every day](https://polygonscan.com/blocks_forked). Many of these are of 10+ depths, which is dangerously high. Due to reorgs, transactions up to 32 blocks ago can be completely reversed. In fact, up until the Delhi update (Jan 17, 2023), it was common to see reorgs up to 128-blocks ago (5 minutes). After the update, this has been reduced to a max of 32 blocks (1 minute). That's better than before the update, but it's still a lot. The reason behind this unique and dangerous Polygon phenomenon is due to the validator sprints that it uses on the Bor block production layer. [I wrote a separate article to explain this phenomenon](https://mplankton.substack.com/p/polygons-block-reorg-problem). > > Even after the Delhi update, there was still a massive [153-block reorg in Feb 2023](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/) and multiple-validator outage caused by an unrelated bug. > > ####**Centralization concerns** > > **Pausable tokens** > > The [MATIC token contract](https://etherscan.io/token/0x7d1afa7b718fb893db30a3abc0cfc608aacfebb0#code) is pausable. There is a private list of addresses (stored in the "_pausers" private role) that can unilaterally pause the entire MATIC token without needing any other members to approve. > > **Centralized control of Polygon contracts on Ethereum mainnet via its Multisig owner account** > > At any given time, Polygon can update its contracts using this Multisig Gnosis Safe, and it has already done so **40 times in the past year** and 170 times in the past 2 years. That's a lot of unannounced updates. > > It does this through a [5 out of 9 Multisig Gnosis Safe](https://etherscan.io/address/0xfa7d2a996ac6350f4b56c043112da0366a59b74c) (often misquoted as an 5 out of 8 Multisig) that controls all of Polygon's contracts on Ethereum (e.g. Plasma Bridge, PoS Bridge, Staking Contract, Governance Proxy, Ether Bridge, Root Chain Proxy, Polygon-to-Ethereum token mapping, and many other contracts). 4 of these owners are Polygon members, 4 are external DeFi users, and 1 is an unknown account (possibly the owner of Quickswap). > > **[My own investigation](https://mplankton.substack.com/p/investigating-the-59-polygon-multisig) discovered that this MultiSig account is one of the worst-documented parts of Polygon**: > > * Every media site, blog, and forum to this day still thinks it's an 5/8 Multisig based on an old letter back in May 2021. The fact that no one has mentioned the 9th owner (added 2 years ago) is a strong sign the public isn't actually auditing the Polygon admin actions on that Multisig contract. > * A 9th owner was added back [in June 2021](https://etherscan.io/tx/0xb02b91300e3cea5bb788513cd858f27f27410b3bc67b8e12dca10944b4d611c8) **unannounced**. An additional 2 Polygon owners were swapped in the past year **unannounced**. > * [Back in Aug 2021](https://etherscan.io/tx/0x9eca1e21c66d7a30bfb69dedb0857314cf7ed127d149328d518678f7e22fbdb9), ownership of all Polygon's contracts were replaced by a [TimeLock contract](https://etherscan.io/address/0xCaf0aa768A3AE1297DF20072419Db8Bb8b5C8cEf). This Timelock provides an acceptance window where any action on Polygon's contracts has to wait 48 hours before it takes effect. The Timelock is in turn controlled by the 5/9 Gnosis Safe account. > * Polygon's websites, forums, Discord channel, and subreddit don't mention the Timelock. > * **Even Polygon's own documentation team is unaware of the Timelock.** There is [one document that mentions the Multisig address](https://wiki.polygon.technology/docs/faq/commit-chain-multisigs/) suggests that a Timelock is a future update, when it's actually already active. > > ####**Upgrade process is centralized** > > Polygon Labs controls the upgrade process through centralized governance. > > Back in Dec 2021, the Polygon team [secretly hard-forked the network](https://cryptobriefing.com/a-hacker-stole-1-6m-after-exploiting-a-polygon-bug/) by pushing out a patch 1 day after a hacker stole $1.6M from the network from the Polygon PoS genesis contract in Dec 2021. The team didn't publicize the reason for the emergency patch until over 3 weeks later. > > In Jan 2023, the **Delhi Hardfork, PIP-7**, was voted on by only [15 out of 100 non-dev validators](https://forum.polygon.technology/t/pre-pip-discussion-addressing-reorgs-and-gas-spikes/10623). The vote was only used as non-binding feedback, so Polygon Lab devs still maintained real control over the upgrade. > > In Feb 2023, there was a client bug that caused [a multi-validator outage and 153-block reorg](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/). Due to the outage and slow syncing where many out-of-sync validators were taking up to a day to resync, many of them were missing their 98% checkpoint SLA requirements for staying on as a validator. As a result, the Polygon team pushed **an emergency proposal, PIP-9**, to reduce the threshold back to 95%. In less than half a day, it passed and was activated. Even over 4 days, only 27 out of 100 validators had voted on it. > > **Future decentralized governance** > > It's been over a year since Polygon posted they were looking into [Governance Decentralization](https://blog.polygon.technology/state-of-governance-decentralization/). It wasn't until only Feb 2023 that they started the first steps towards decentralized governance via [PIP-1](https://forum.pol... ***** Would you like to learn more? Check out the [Cointest archive](/r/CointestOfficial/wiki/cointest_archive#wiki_Polygon) to find submissions for other topics.

CointestMod

#Polygon Con-Arguments Below is a Polygon con-argument written by a deleted user. > ####**Has plenty of competitors, including itself** > > Currently, Polygon PoS is competing against optimistic L2 blockchains like Arbitrum One and Optimism. Arbitrum has nearly [2x the TVL as Polygon](https://defillama.com/chains), and Optimism has almost caught up. > > Polygon's future zkEVM rollup is also competing against other zkEVM rollups. Once its zkEVM is released, it's possible it's going to split the Polygon community between those who want to stay on the sidechain and those who want to use the zkEVM. **If you look at their [zkEVM testnet](https://explorer.public.zkevm-test.net/txs?block_number=143530&index=0&page_number=1&page_size=50&pages_limit=200), fees are paid in Ether, not MATIC.** That's bearish for MATIC token utility. > > **TVL has dropped considerably compared to L2s** > > One year ago back in Jan 2022, [Polygon TVL was $4.8B USD](https://defillama.com/chain/Polygon) while the combined [Layer 2 rollup TVL was $5.4B USD](https://l2beat.com/scaling/tvl). While L2 TVL has increased a little despite the bear market, Polygon's TVL has collapsed by 75% to $1.2B. > > **Growing dApp competition from L2 rollups** > > A year ago, Polygon PoS was unique in that it was the only network besides Ethereum that had OpenSea support. Now OpenSea supports a dozen different networks, including competing Layer 2 rollups networks like Optimism, Arbitrum One, and even Arbitrum Nova. So there's a lot more competition. > > **Declining social media support** > > With L2 rollups developing so quickly, many in the Ethereum community have turned against Polygon, creating a narrative that it's "just a sidechain", not a true Layer 2. > > The 0xPolygon subreddit has become more of a ghost town with noticeable amounts of spam posts. I don't think its mods are checking regularly anymore. > > ####**Less resistant to DDoS attacks and spam** > > Like all networks with low transaction fees, it's at risk of DDoS attacks. > > In early Jan 2022, [Sunflowers Farm \(SFF\) unintentionally DDoS-attacked the Polygon PoS network](https://www.coindesk.com/tech/2022/01/06/polygon-under-accidental-attack-from-swarm-of-sunflower-farmers/) and completely congested the network because it was more profitable to play the game and spam transactions than pay network fees. Transaction fees shot up 20x. Eventually, a hacker exploited the SFF game and reduced its price to zero, and users rejoiced because it cleared the congestion. > > **It has a Gas Cartel** > > Spam attacks were eventually mitigated when the whole Polygon validator community chose to [lock priority fees at a 30 Gwei minimum](https://cryptoslate.com/polygon-matic-to-raise-gas-fee-to-30-gwei-to-prevent-spam-transactions/). That's not an offical part of protocol. Polygon validators have colluded off-chain and are running **gas cartel**, like OPEC. > > However, it still gets tons of spam transactions, which I have experienced first-hand many times. All my Polygon accounts with activity on them were randomly sent spam tokens and NFTs. Many of these tokens are part of scam that try to trick you into interacting with them by selling them. Other are advertising sketchy website links. > > This is the downside of having sub-penny transactions. > > ####**Still requires the Ethereum network** > > The Polygon PoS network is a side chain for Ethereum. Many parts of Polygon still require Ethereum and pay fees in ETH instead of MATIC. OpenSea's NFT are usually quoted in ETH instead of MATIC. The MATIC token its originates on Ethereum and is bridged over to Polygon PoS as an ERC-20 token. Staking is also done on the Ethereum mainnet. The periodic Polygon checkpoints require paying Ethereum fees too. > > Thus Polygon's success depends on Ethereum's success and security. > > Going from Layer 1 Ethereum to Polygon is mainly done through the Polygon PoS bridge, which costs Ethereum gas fees. The first time bridging over to Polygon can be stressful. Their documentation says it should only take [22-30 minutes](https://wiki.polygon.technology/docs/develop/ethereum-polygon/getting-started/) when it often takes many hours as many people including me have found out the hard way. > > ####**Numerous reorgs** > > Polygon has [multiple reorgs every day](https://polygonscan.com/blocks_forked). Many of these are of 10+ depths, which is dangerously high. Due to reorgs, transactions up to 32 blocks ago can be completely reversed. In fact, up until the Delhi update (Jan 17, 2023), it was common to see reorgs up to 128-blocks ago (5 minutes). After the update, this has been reduced to a max of 32 blocks (1 minute). That's better than before the update, but it's still a lot. The reason behind this unique and dangerous Polygon phenomenon is due to the validator sprints that it uses on the Bor block production layer. [I wrote a separate article to explain this phenomenon](https://mplankton.substack.com/p/polygons-block-reorg-problem). > > Even after the Delhi update, there was still a massive [153-block reorg in Feb 2023](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/) and multiple-validator outage caused by an unrelated bug. > > ####**Centralization concerns** > > **Pausable tokens** > > The [MATIC token contract](https://etherscan.io/token/0x7d1afa7b718fb893db30a3abc0cfc608aacfebb0#code) is pausable. There is a private list of addresses (stored in the "_pausers" private role) that can unilaterally pause the entire MATIC token without needing any other members to approve. > > **Centralized control of Polygon contracts on Ethereum mainnet via its Multisig owner account** > > At any given time, Polygon can update its contracts using this Multisig Gnosis Safe, and it has already done so **40 times in the past year** and 170 times in the past 2 years. That's a lot of unannounced updates. > > It does this through a [5 out of 9 Multisig Gnosis Safe](https://etherscan.io/address/0xfa7d2a996ac6350f4b56c043112da0366a59b74c) (often misquoted as an 5 out of 8 Multisig) that controls all of Polygon's contracts on Ethereum (e.g. Plasma Bridge, PoS Bridge, Staking Contract, Governance Proxy, Ether Bridge, Root Chain Proxy, Polygon-to-Ethereum token mapping, and many other contracts). 4 of these owners are Polygon members, 4 are external DeFi users, and 1 is an unknown account (possibly the owner of Quickswap). > > **[My own investigation](https://mplankton.substack.com/p/investigating-the-59-polygon-multisig) discovered that this MultiSig account is one of the worst-documented parts of Polygon**: > > * Every media site, blog, and forum to this day still thinks it's an 5/8 Multisig based on an old letter back in May 2021. The fact that no one has mentioned the 9th owner (added 2 years ago) is a strong sign the public isn't actually auditing the Polygon admin actions on that Multisig contract. > * A 9th owner was added back [in June 2021](https://etherscan.io/tx/0xb02b91300e3cea5bb788513cd858f27f27410b3bc67b8e12dca10944b4d611c8) **unannounced**. An additional 2 Polygon owners were swapped in the past year **unannounced**. > * [Back in Aug 2021](https://etherscan.io/tx/0x9eca1e21c66d7a30bfb69dedb0857314cf7ed127d149328d518678f7e22fbdb9), ownership of all Polygon's contracts were replaced by a [TimeLock contract](https://etherscan.io/address/0xCaf0aa768A3AE1297DF20072419Db8Bb8b5C8cEf). This Timelock provides an acceptance window where any action on Polygon's contracts has to wait 48 hours before it takes effect. The Timelock is in turn controlled by the 5/9 Gnosis Safe account. > * Polygon's websites, forums, Discord channel, and subreddit don't mention the Timelock. > * **Even Polygon's own documentation team is unaware of the Timelock.** There is [one document that mentions the Multisig address](https://wiki.polygon.technology/docs/faq/commit-chain-multisigs/) suggests that a Timelock is a future update, when it's actually already active. > > ####**Upgrade process is centralized** > > Polygon Labs controls the upgrade process through centralized governance. > > Back in Dec 2021, the Polygon team [secretly hard-forked the network](https://cryptobriefing.com/a-hacker-stole-1-6m-after-exploiting-a-polygon-bug/) by pushing out a patch 1 day after a hacker stole $1.6M from the network from the Polygon PoS genesis contract in Dec 2021. The team didn't publicize the reason for the emergency patch until over 3 weeks later. > > In Jan 2023, the **Delhi Hardfork, PIP-7**, was voted on by only [15 out of 100 non-dev validators](https://forum.polygon.technology/t/pre-pip-discussion-addressing-reorgs-and-gas-spikes/10623). The vote was only used as non-binding feedback, so Polygon Lab devs still maintained real control over the upgrade. > > In Feb 2023, there was a client bug that caused [a multi-validator outage and 153-block reorg](https://www.coindesk.com/tech/2023/02/22/polygon-blockchain-suffers-apparent-outage/). Due to the outage and slow syncing where many out-of-sync validators were taking up to a day to resync, many of them were missing their 98% checkpoint SLA requirements for staying on as a validator. As a result, the Polygon team pushed **an emergency proposal, PIP-9**, to reduce the threshold back to 95%. In less than half a day, it passed and was activated. Even over 4 days, only 27 out of 100 validators had voted on it. > > **Future decentralized governance** > > It's been over a year since Polygon posted they were looking into [Governance Decentralization](https://blog.polygon.technology/state-of-governance-decentralization/). It wasn't until only Feb 2023 that they started the first steps towards decentralized governance via [PIP-1](https://forum.pol... ***** Would you like to learn more? Check out the [Cointest archive](/r/CointestOfficial/wiki/cointest_archive#wiki_Polygon) to find submissions for other topics.

CointestMod

#Polygon Con-Arguments Below is a Polygon con-argument written by a deleted user. > ####**Has plenty of competitors, including itself** > > Currently, Polygon PoS is compe