chainlist VS snapshot

Head to coinmarketcap Search for donut You'll see contract, copy the one from gnosis network Head to your metamask and add gnosis network using this Switch to gnosis after adding it to your metamask Click on add token and paste the donut contract then add it

You can check out a list of EVM chains here: https://chainlist.org/

I don't care if my transaction is leaked as long as my secret phrases are safe. Is it possible to leak your SP through a RPC? For example, there are many RPCs on https://chainlist.org/ And they have a security score for each one. Should I be worried about a low score?

# Helper function that checks a single node def get_last_block_once(rpc): try: w3 = Web3(Web3.HTTPProvider(rpc)) block_number = w3.eth.block_number if isinstance(block_number, int): return block_number else: return None except Exception as e: print(f'{rpc} - {repr(e)}') return None # Main function to check the status of the service that will be called def check_service(): # pre-prepared list of reference nodes # for any network, it can be found on the website https://chainlist.org/ list_of_public_nodes = [ 'https://polygon.llamarpc.com', 'https://polygon.rpc.blxrbdn.com', 'https://polygon.blockpi.network/v1/rpc/public', 'https://polygon-mainnet.public.blastapi.io', 'https://rpc-mainnet.matic.quiknode.pro', 'https://polygon-bor.publicnode.com', 'https://poly-rpc.gateway.pokt.network', 'https://rpc.ankr.com/polygon', 'https://polygon-rpc.com' ] # parallel processing of requests to all nodes with multiprocessing.Pool(processes=len(list_of_public_nodes)) as pool: results = pool.map(get_last_block_once, list_of_public_nodes) last_blocks = [b for b in results if b is not None and isinstance(b, int)] # define the maximum and median value of the current block med_val = int(np.median(last_blocks)) max_val = int(np.max(last_blocks)) # determine the number of nodes with the maximum and median value med_support = np.sum([1 for x in last_blocks if x == med_val]) max_support = np.sum([1 for x in last_blocks if x == max_val]) return max_val, max_support, med_val, med_support

With this said, chainlist.org is a commonly referenced site too. Just sharing what is in the documentation for MM :) .

3: You now need to add the Optimism network into Metamask. Go to chainlist.org, "connect wallet" (connect with Metamask), search for Optimism, click add to Metamask, approve, switch network. You'll now be on optimism.

https://chainlist.org add chains with 1 click pretty much

You can also add the network you want to test in advance. How to add these test networks quickly? First, you can open https://chainlist.org/, check “Include Testnets”, search for the corresponding test network, and add it directly to your wallet.

Infura provides what's called an RPC endpoint. RPC is the way you expose a node to people who want to talk to it from a web browser etc. You can run your own node, using a normal computer, but it needs a big SSD drive (around 2TB) which costs a couple of hundred dollars. If you want to use a node hosted by somebody else, there are lots of other companies providing them. A good one is Alchemy. You can see a long list of publicly available RPC nodes for Ethereum (and also similar lists for other chains) at https://chainlist.org/

For the conecil, I think a governance platform like snapshot.org could be helpful for community proposals. That way it's more inclusive of all Coneheads.

VOTE HERE: https://snapshot.org/#/dogelondao.eth/proposal/0xf988aff67d371c72e4d08a6a3784b20d314ab53a9456a149fe2e57d665f7219c

Right now there is only one synthetic token - USDT (USDT). Its underlying asset, the price of which is linked to the price of synthetics - Tether USDT. In the future, we will issue various synthetic tokens, the underlying asset of which can be stocks, fiat currencies (how do you like a styblecoin tied to the Euro?), indices and portfolios, including all of the above in different proportions. We look forward to the community's help in choosing the underlying assets when designing new synthetics. I believe that we will provide some kind of voting mechanism for this (for example, based on https://snapshot.org ) using the TTP token as a voting token.

PART-2 I'm bringing the conversation from discord here to just update this as we discuss this and how this is on the record. u/mocolicious — I appreciate your contribution to the discussion. so first, we would have to get people to agree that this is what the community wants to do via the governance voting. After that, the owner of the upgrade authority would have to grant access to the keys. Im not sure if thats possible or who that might be. I think the move is to wait til the governance solution has been tested on some more simple propositions and then we can make a stronger argument about inquiring to who owns it. Else we're talking about starting a new token entirely with the same name, which would also be a difficult proposition. u/CitizenCapet — I'm certainly in favor of seeing if we can update the contract without creating a new KIN. You did raise some valid points. Implementing a transfer burn mechanism in the existing KIN contract without creating a new token will require community consensus and potentially involve some technical and governance challenges. I did some research and this is what could be some possible approaches to address these points: Community Consensus: As you mentioned, it's crucial to ensure that the majority of the KIN community agrees with the proposed changes. Implementing a governance voting mechanism or using an existing one you are developing now, when available, would allow token holders to voice their opinions and vote on the proposal. I wish we could use a pre-existing one that was free and verifiable for KIN holders to use. I found pre-existing blockchain voting protocols that could be utilized for KIN holders to vote on proposals like implementing a transfer burn mechanism. Some of these protocols are free and verifiable, ensuring a transparent and decentralized decision-making process. four voting-free blockchain protocols that KIN can use today if we tinker with them. 1A. Aragon https://aragon.org/ is a platform for creating and managing decentralized organizations. It offers a suite of tools for governance, including voting mechanisms. KIN could potentially create an Aragon organization and use its voting module to let KIN holders vote on proposals. 2B. Snapshot https://snapshot.org/ is a gasless, off-chain voting platform for decentralized governance. Projects can create proposals and let their token holders vote on them using their token balance without incurring gas fees. KIN could create a Snapshot space for the community to vote on proposals. 3C. DAOstack https://daostack.io/ is a framework for building decentralized organizations and managing their governance. It includes a voting module called "Alchemy" which enables token holders to vote on proposals. KIN could potentially utilize DAOstack to create a DAO for managing the project's governance, including voting on proposals. 4D. Colony https://colony.io/ is a platform for building decentralized organizations with built-in governance features. KIN could potentially create a Colony organization and utilize its voting mechanisms to let token holders vote on proposals. Upgradeable smart contracts: If the current KIN smart contract is upgradeable (e.g., implemented using a proxy pattern or similar mechanism), updating the contract to include the transfer burn mechanism would be more straightforward. The upgrade authority would need to authorize the changes, and the new logic would be implemented without affecting the existing token holders' balances or creating a new token. Which I would like to avoid for obvious reasons. Identifying the upgrade authority: To update the smart contract, it's essential to determine who holds the upgrade authority. This could be the project team, a multisig wallet, or a DAO. It might be necessary to wait for the governance solution to be more mature and tested before approaching the upgrade authority with the proposal. But voting on something and implementing it are two things. Non-upgradeable contracts: If the current KIN contract is not upgradeable, implementing the transfer burn mechanism directly within the existing contract may not be possible. In this case, creating a new token with the same name and implementing a token swap mechanism might be a potential solution, though it would indeed be a complex and challenging process. There has to be a way around this. I'm certain this is solvable. @mocolicious — without access to the key with upgrade authority you'd need to create a new token @CitizenCapet — So no one knows who has the key with upgrade authority? How it this even possible being this is an open-source ecosystem? Wouldn't TED have an idea? @mocolicious — it would be a safe presumption that he has it, but you'd have to ask him @CitizenCapet — Well then, I shall ask him. _____________________________________________________________________________________________ In closing, my goal is to get feedback to help the discussion grow in optics and provide any material the community is requesting. I can build almost anything. As long as I have clear instructions as to what is being requested to add. Be cool to have some devs that want to help with the code and debugging once we get the final optics on parameters.

Fixed inability to connect Brave Wallet to https://snapshot.org. (#28896)

Snapshot

However, voicing your opinion in the comments of a governance poll alone DOESN'T count as if you were casting your vote. To do so, you have to click the link on the beginning of the post, access snapshot.org and cast your vote there.

Have you heard of https://snapshot.org?

How to obtain CAKEVOTES to vote https://snapshot.org/ ?