Monero

I do not know that much about Crypto Currency. But as far as I understand:

• Whenever a new block is mined a list of transactions is executed. This means transaction speed depends on the rate with which new blocks are mined. What is that rate for Monero?
• Difficulty of the proof of work algorithm to mine new blocks is adjusted to keep the rate as constant as possible

Is there something in Monero transactions that can tie them together in this scenario:

• send some non-private crypto to an instant exchange
• exchange it for monero
• withdraw the monero
• after some time send some monero to that same instant exchange to exchange it for some non-private crypto

Would the instant exchange have a way to determine if the two transactions are connected to the same wallet (amounts being different)? What time difference between the 2 transactions would be sufficient?

US government ready to apply the PATRIOT Act to Bitcoin and digital assets The FinCEN Director confirms that the Treasury is finalizing a ban on privacy tools for Bitcoin and cryptocurrencies.

According to The Rage, this week marks a pivotal moment for the digital asset sector in the United States, with the government preparing to apply the PATRIOT Act to Bitcoin and other cryptocurrencies. While last week brought positive developments on reforms to the Bank Secrecy Act of 1970, worrying news now emerges regarding the privacy of bitcoin and crypto transactions.

The PATRIOT Act, enacted after September 11, 2001, under the Bush administration, grants the U.S. government extraordinary powers to bypass constitutional protections in the event of terrorist threats. These powers include warrantless surveillance and the suspension of the right to a fair trial.

According to reports, FinCEN Director Andrea Gacki confirmed that the Treasury is working to finalize the so-called “mixer rule.” This regulation aims to ban nearly all privacy mechanisms on public blockchains for U.S. citizens.

During the hearing, Representative Liccardo stated: “We are seeing more and more illegal transactions being done in crypto,” citing a study showing that 91% of 111 fraud cases examined involved decentralized finance (DeFi). The main concern is the pseudonymity of transactions.

Gacki responded that FinCEN is collaborating with blockchain analytics firms to de-anonymize pseudonymous transactions, but Liccardo countered that software like mixers could allow users to evade even the most sophisticated detection techniques. Bitcoin privacy under attack

Contrary to its name, the Treasury’s mixer rule is not limited to mixers, but represents a generalized ban on any software or behavior that provides transactional privacy to users of public blockchains such as Bitcoin.

The rule would consider the following activities a “primary concern for money laundering”:

pooling or aggregating crypto from multiple people, wallets, or accounts;
using computer code to coordinate or manipulate the structure of transactions;
splitting Bitcoin to transmit it across independent transactions;
creating disposable wallets, addresses, or accounts;
exchanging between different types of cryptocurrencies;
facilitating delays in transactional activity.

These provisions could also put Bitcoin users employing common privacy practices under suspicion, potentially leading to criminal liability similar to traditional finance smurfing—the breaking up of large sums of money into smaller transactions to evade banking controls—a federal offense punishable by up to five years in prison. Revival of the Special Measures to Fight Modern Threats Act

Parallel to FinCEN’s work, the Special Measures to Fight Modern Threats Act, previously considered stalled in Congress, has been reintroduced. Representative Zach Nunn confirmed that the bill is still under debate.

According to The Rage, the Special Measures to Fight Modern Threats Act, originally introduced in 2022 by Representative Himes of Connecticut, would effectively give the Treasury the power to prohibit any transaction deemed concerning without public notice or consultation.

As highlighted by The Rage contributor Nicholas Anthony, who has written for the Cato Institute, “one likely scenario is that the Treasury would use this authority to prohibit U.S. banks from being involved with cryptocurrency transactions validated by miners located outside of the United States.”

Jerry Brito and Peter van Valkenburgh of CoinCenter described this approach as “dangerously authoritarian,” noting that all cryptocurrencies are inherently global and therefore any Bitcoin transaction could plausibly be linked to a foreign jurisdiction.

The post US government ready to apply the PATRIOT Act to Bitcoin and digital assets appeared first on Atlas21.

Source: https://njump.me/naddr1qq5xzjzjxp35snfkf3unj6rygauxscm6f9uycm2wwe39xwp0vdzrq72d0f3nynt8857szxthwden5te0wfjkccte9eekummjwsh8xmmrd9skctczyr4sz4a07wgqx9hy4ecu49vpy46k47038va0qh7hmsfs7ymh4dk92qcyqqq823cxt3wlc

More community input is needed on possible deployment of temporary rolling DNS checkpoints to defend against Qubic attacks: https://github.com/monero-project/monero/issues/10064

Please comment on the GitHub issue and/or click thumbs-up/down emoji reaction.

TL;DR: A malicious mining pool is disrupting the network and could cause deep blockchain re-organizations. DNS checkpoints, which have existed for emergency use in the code since 2014, could prevent deep blockchain re-organizations, but Monero's blockchain consensus protocol would temporarily be less decentralized.

Advantages

Practical advantages

• The code for this countermeasure has been in the Monero codebase for over ten years. The countermeasure is ready to deploy now, once final testing, "procedure smoothing" (see below) and successful outreach to honest mining pools is completed.

• Humans (i.e. the Monero Core Team) could intervene by ceasing or modifying the checkpointing procedure if the checkpointing produces undesirable results.

Principled advantages

• Rolling DNS checkpoints could keep the Monero network working, with minimum disruption, for the thousands of users who depend on it every day for private peer-to-peer electronic cash.

Disadvantages

Practical disadvantages

• Rolling DNS checkpointing has never been deployed on Monero's mainnet before. Something unforeseen could go wrong.

• Successful checkpointing requires most of the major honest Monero mining pools to voluntarily enable DNS checkpointing enforcement. If the mining pools choose not to, rolling DNS checkpoints will likely be unsuccessful.

• Maintaining control of the DNS records would require strict security procedures. Two previous security incidents in 2019 and 2023 involving malicious software hosted on getmonero.org servers and theft of community donated funds should be kept in mind.

Principled disadvantages

• Without a doubt, Monero's consensus mechanism would be less decentralized if rolling DNS checkpoints were enabled.

• Monero nodes would temporarily no longer follow the chain with the most proof of work.

• Mining pools following the DNS checkpoints would be similar to a situation of the majority of mining hashpower coordinating and colluding against a minority hashpower miner. "Majority hashpower cannot collude" may be considered a security assumption of proof-of-work consensus.

P2Pool v4.10 speed up the whole Monero network

If you're still mining on a normal pool like in the old days, your computer has to wait much longer to receive its work from the internet. With p2pool, it takes a fraction of the time of regular centralized pools!

How it will work with P2Pool broadcasts:

• 1. A pool or a solo miner finds a block, then submits it to their Monero node
• 2. Monero node notifies its connected P2Pool node of a new block (instantly)
• 3. P2Pool network spreads this block across all peers, spending only 2-3ms on each hop
• 4. All P2Pool peers submit this block to their respective Monero nodes
• 5. These Monero nodes verify this block in parallel - this is where the time saving comes from

As soon as enough P2Pool miners update to v4.10 or newer, block propagation times in the whole Monero network will reduce significantly.

➡️ Reddit

./monerod --zmq-pub tcp://127.0.0.1:18083 --out-peers 32 --in-peers 64 --add-priority-node=p2pmd.xmrvsbeast.com:18080 --add-priority-node=nodes.hashvault.pro:18080 --enforce-dns-checkpointing --enable-dns-blocklist

Hi all, circling back on my last post. After reviewing suggestions and testing other services, I’ve narrowed it down to 2 solutions.

Clockswap (0.5% fees) and Wizardswap (3.2% fees)

I'd personally go for Clock. They got bigger pools and better rates but it’s good to have a mix of options.

Let me know what you think.

Wtf is going on with kraken?

https://status.kraken.com/incidents/rzd4fm71v33m

Currently we have paused Monero (XMR) withdrawals.
Deposits are unaffected and still require 32 confirmations (~1h) before crediting.
We are actively monitoring the situation and will provide more updates as they become available.

The last update was 2 days ago, basically it's been down for a week.

Hello all,

I'm excited to announce launch of XMR.CARDS service. We offer gift cards for 2000+ brands, 60+ countries. We don't require KYC and support Tor for maximum anonymity.

Please let me know about your thoughts and recommendations, we have just launched and open for all thoughts!

Website: https://xmr.cards/

Tor: http://xmrcards7pb5dnj5dfbnueigmzwgujwlo5zhd6f3vnlhay6qlbd3dzid.onion/

(cross-posted from reddit)

github presentation of the FCMP++ audits w.r.t. the modules in the codebase

If It Isn't PoW, It Isn't Decentralized w/ Dr. K Tune-in to a LIVE MoneroTalk episode Tonight 9/5 at 7PM-EST!

Watch here on X or on YT➡️: https://www.youtube.com/live/bRpZxxDHAiY TWITCH ➡️: twitch.tv/monerotalk Now streaming on Rumble!➡️: rumble.com/user/monerotalk

Thank you to our show sponsors cakewallet.com / stealthex.io /

Vini Barbosa’s unfiltered take on the Monero selfish mining attacks and PoW (MT 360)

TODAY'S 🎙SHOW: Douglas Tuman has a discussion with Vinny Barbosa, a Brazilian crypto writer and privacy advocate, about the current challenges facing the Monero network, particularly the ongoing selfish mining attacks by the Qubic pool. The conversation explores both short-term and long-term solutions, including the proposed "Publish or Perish" soft fork to disincentivize selfish mining, defensive mining strategies, and the controversial idea of incorporating proof-of-stake elements or a finality layer to enhance network security. Vinny argues that while Monero’s proof-of-work and ASIC resistance are valuable for decentralization and permissionless mining, all proof-of-work systems are inherently vulnerable to such attacks, and the community should remain open to researching hybrid or alternative consensus models without ideological dogma. The dialogue emphasizes the importance of open debate, technical innovation, and community resilience in navigating Monero’s current crisis, while also touching on broader themes of digital cash, sovereignty, and interoperability with other privacy and scalable cryptocurrencies like Zcash and Nano.

Watch Here (YouTube)➡️ https://youtube.com/live/5wpVcq8e5vs Listen Here 🎧: https://www.monerotalk.live/monerotalk-360

Coffee & Monero, Go to Gratuitas.org today!

FOLLOW US https://monero.town/u/monerotalk & https://mastodon.social/@monerotalk

Thank you to sponsors, u/cakelabs and u/Stealthex_io as well as u/sunchakr for making these interviews possible! And of course our listeners and supporters for making Monero Talk possible!

Podcasts 🎧 :

iTunes: https://podcasts.apple.com/us/podcast/monero-talk/id1445930212 Spotify: https://open.spotify.com/show/60lQ05X8lcuXv71fhi6hl7

If you enjoy our show please Subscribe, Like, Share, Rate our YouTube Channel & Podcasts. This will help us grow and spread Monero content!

We were huge fans of LocalMonero's weekly blog series, "The Monero Standard" and missed it after they shut down. It was too valuable of a resource for the community to just disappear.

So we decided to continue it.

Here is the first new edition, published on our blog at Cyphergoat: https://cyphergoat.com/blog/monero-standard-1

A quick note on the name: We're not the original team, but they've kindly given us permission to continue using "The Monero Standard"

We'll be publishing a new summary every week. Let us know what you think!

WebWipe is hosting another privacy pop-up event, this time in Nashville, TN on September 20th (Saturday)

6-10 PM @ Diskin Cider (1235 Martin Street Nashville, TN 37203)

Come join us discussing privacy and the latest news on Monero and other privacy tools while enjoying a local cidery in Music City.

We'll have presentations on some of these topics and discuss others

• Eigenwallet demo
• Edge Wallet presentation
• Retoswap demo
• Bisq and robosats presentations
• OrangeFren demo
• Ashigaru presentation with Dojobay demo
• Ashigaru Whirlpool demo
• RoninDojo and Boltzmann calculator demo
• Cakewallet presentation
• Nym's Mixnet and NymVPN presentation
• encrypted communications and groups using SimpleXchat
• XMRBazaar demo
• Passphrase magazine and other swag

& more

Free to attend

I have recently seen some heated debates about Proof of Stake and Monero.
I think we are missing some clarification to make sure we are all discussing the same things. Let's chat about this so we can all contribute to improve the network.

The Monero network has recently seen some mining centralization.
As a hostile mining pool, the attacker has some attack vectors that can cause more or less disruption, and that disruption needs to be addressed, carefully. This comment on lemmy explains this point in more details.

One of the disruptions caused by the attacker is deep block re-orgs, that cause exchanges like Kraken to increase deposit times for Monero (details also in post above).
One of the solutions proposed to resolve this issue is to record somewhere that a block is accepted, and it should not be changed in the future. Something that says, we solemnly declare that this block is in its final state, and we won't change it anymore.

Of course, we are not going to the city hall for that, we need a way to do it in a decentralized and trust-less way. But wait, we actually already have a solution for the problem of aligning different actors that have trouble communicating and agreeing on things, in a decentralized way: a blockchain. We could use a blockchain to say that this or that Monero block is finalized and no block re-org can change it.
If we go with that option, it needs to be a different blockchain, it needs to generate blocks faster than the Monero network, and it needs to be secure enough for this use case (for example, that blockchain should not itself have many deep block re-orgs).
Considering this, POW blockchains tend to have longer block times and might be just as susceptible to block re-orgs. More info in this lemmy post.

This is where Proof of Stake comes in as an option for a place to record that a given Monero block is finalized.
There are many things to consider before jumping into this, but this is the general idea.

That discussion is not about moving Monero to a Proof of Stake model with anointed super validators that can punish bad miners, and that will soon start judging and punishing naughty users too.
That is an entirely different thing and nobody is seriously considering doing that.

The PoS finality layer is just one of the options on the table to fix issues on the network. It isn't even the easiest or fastest to implement if we just want to deal with the current situation.

Another important point is that even in the scenario of a PoS finality layer, RandomX stays. This finality layer thing is not about making Monero a PoS coin, it's about using some other PoS to record things about the POW RandomX Monero as we know it currently.

All the options need to be considered and feel free to post your ideas here or on GitHub or on the Monero Research Labs chats. The worst thing that could happen is that only very few people learn and participate in those discussions and people like you and me exclude ourselves from the discussions because we don't know enough about it.

There is something that is clear though, some parts of the network are not yet completely ready for attacks by annoyed state actors. Right now the attacker does not seem like the proxy of very annoyed actors, and we have time for some adaptations. We might not have that much time during the next attacks, so we also need to chose solutions that will be useful in that scenario.

So, what do you think of using a PoS finality layer for Monero ?

Personally I think that if you directly apply these conditions for a PoS finality layer, you end up on the bright idea of using something like Ethereum or Litecoin. The Monero community does NOT want to have to rely on ETH or LTC for security. That would feel like a huge blow and a huge let-down…

But yeah, if need be, for me, this is still a perfectly acceptable temporary solution.

Now that my go-to exchange Tradeogre has been fedded, I'm looking for alternatives to swap relatively good amounts from and to XMR.

I've heard bad stories about ChangeNOW, Changelly, and FixFloat. On Reddit are full of posts where people accuse them of being scams or having funds locked. (Same happened to a friend)

Hopefully someone here has some good suggestions.

Hello there, fellow Monero addicts. By now, I'm sure everyone is aware of the Qubic attack on Monero.

I’ve started a discussion on GitHub about what I believe is the true objective of this attack. If you're interested, please read the short discussion-we can continue it here, as it was closed on GitHub (it wasn’t the right place for such discussions).

I’m curious to hear your opinions.

Join us TMRW (SUN 8/24) at 11AM-EDT/5PM-CET for MoneroTopia EPI 228 +Price 📈 Bawdy Anarchist, News 🗞️ w/ Tony Huszar & MORE!

👀➡️:https://www.youtube.com/live/ctCRHiInfvQ Join ➡️: streamyard.com/b4bujf8zuw

Sponsors🙏 🎢cakewallet.com 🎢WizardSwap.io 🎢exolix.comm 🎢XMR.BAR

In case you missed it, this report by Shai Deshe confirmed that Qubic had around 35% of the Monero hashrate.
They did not get more than 50% of the hashrate.

The important point is not that they didn't get 51%. The important point is that Monero is supposed to be alphabet-hammer resistant but this experience has exposed glaring vulnerabilities in those aspects.

I personally disagree with Shai's views in the Interpretation and Conclusion section. There, he advocates for ASIC friendlyness as a countermeasure. His view is, for a given algorithm, ASIC hardware is very limited in quantity, and it would be way too expensive and impractical to buy new hardware to make an attack on the network. In his view, with ASIC resistance, it's very easy for bad actors to get hashrate for an attack.

I don't agree because as Shai pointed out, Qubic brought new hardware from new hardware, but that was a bit above 5% (under some assumptions). Most of their hashrate came from bribing existing miners into switching to a more lucrative pool. Given that, ASIC friendliness does not help if your miners switch allegiance for more coins in their pockets. And the community will not be able to crowd-fund their way into fighting back. In case the attacker faces a true believer mining pool ready to loose money by not joining the attackers, the attackers can always consider getting a wrench and applying some physical pressure to the pool operators so that they switch. Remember, the pool of hardware is limited, controlling that hardware is controlling the network and in this case, no community funded outside help is coming...

Running your own Monero node enhances privacy, supports the network, and allows you to verify transactions independently.

Warning: Syncing the Monero blockchain requires significant resources: ~100 GB disk space (pruned), and a stable internet connection. Initial sync may take days, but with NVMe drives it takes around a day. Exposing RPC publicly (as in this script below) requires strong authentication—use a secure password within the script and consider firewall rules.

Steps to Set Up and Prepare OS (Debian in my case): Download and Extract Monero CLI:

Go to https://www.getmonero.org/downloads/ and copy link for the Linux CLI package (e.g., monero-linux-x64-v0.x.x.x.tar.bz2).

wget https//.... # download via cli
mkdir -p ~/monero
tar -xvf monero-linux-x64-v0.x.x.x.tar.bz2 -C ~/monero

This places monerod in ~/monero/monerod. Make it executable:

chmod +x ~/monero/monerod

Save the following modified script as run_monero_node.sh in your home directory (or anywhere convenient).

READ THE SCRIPT CAREFULLY

#!/bin/bash
set -euo pipefail

#
***
Configuration
***
# Base directory for Monero files (adjust if needed)
MONERO_BASE_DATA_DIR="${HOME}/monero"
MONERO_DATA_DIR="${MONERO_BASE_DATA_DIR}/.bitmonero"
MONERO_BIN="${MONERO_BASE_DATA_DIR}/monerod"  # Path to the monerod binary

# RPC credentials, used in wallets (CHANGE THESE to secure values!)
RPC_USER="your_rpc_username"  # e.g., "monero_user"
RPC_PASS="your_strong_password"  # Use a long, random password

# Create data directory if it doesn't exist
mkdir -p "${MONERO_DATA_DIR}"

# Check if monerod binary exists
if [ ! -f "${MONERO_BIN}" ]; then
    echo "Error: The Monero binary could not be located at: ${MONERO_BIN}"
    echo "Please download the Monero CLI from getmonero.org, extract it to ${MONERO_BASE_DATA_DIR}, and try again."
    exit 1
fi

# Check if monerod is executable
if [ ! -x "${MONERO_BIN}" ]; then
    echo "Error: The Monero binary at ${MONERO_BIN} does not have execute permissions."
    echo "To fix this, run the command: chmod +x \"${MONERO_BIN}\" and then retry."
    exit 1
fi

# Command to run monerod with optimized settings
# - Pruned blockchain to save space (~1/3 full size)
# - RPC exposed on all interfaces (0.0.0.0) with auth—secure your firewall!
# - Priority nodes for faster sync
# - ZMQ for tools like P2Pool
# - In/out peers tuned for performance
MONEROD_COMMAND=(
    "${MONERO_BIN}"
    --data-dir "${MONERO_DATA_DIR}"
    --rpc-login "${RPC_USER}:${RPC_PASS}"
    --rpc-restricted-bind-ip=0.0.0.0
    --rpc-restricted-bind-port=18089
    --add-priority-node=p2pmd.xmrvsbeast.com:18080
    --add-priority-node=nodes.hashvault.pro:18080
    --disable-dns-checkpoints
    --confirm-external-bind
    --enable-dns-blocklist
    --check-updates=disabled
    --no-igd  # Disable UPnP port mapping
    --in-peers=64
    --out-peers=32
    --zmq-pub="tcp://127.0.0.1:18084"  # For P2Pool integration
    --prune-blockchain
    # Notes:
    # - Default P2P port: 18080 (firewall: allow inbound if public)
    # - Default unrestricted RPC port: 18081 (not used here)
)

# Run the command
exec "${MONEROD_COMMAND[@]}"

If you planning to use p2pool, use it on the same server, --zmq-pub="tcp://127.0.0.1:18084" only exposes the port on locahost.

Make the Script Executable:

chmod +x run_monero_node.sh

To run in background: Use screen, tmux, or nohup ./run_monero_node.sh &.

Secure Your Server with UFW

sudo apt update
sudo apt install ufw

Deny all incoming traffic by default (blocks everything unless explicitly allowed) and allow all outgoing traffic (your node needs to connect out to peers):

sudo ufw default deny incoming
sudo ufw default allow outgoing

Allow ssh port (22) and any other port you plan to use:

sudo ufw allow 22/tcp
sudo ufw allow 18080/tcp # recommended to contribute to the Monero network
sudo ufw allow 18089/tcp # Optionally allow restricted RPC (port 18089) if you need remote access
 
# enable firewall:
sudo ufw enable
sudo ufw status verbose

If you have RPC enabled now you can also connect wallets by pointing to http://your_server_ip:18089 with RPC credentials.

NOTE: If you want to host the node on a remote server I recommend to use Datalix servers, they offer top ups via Monero!

I'm on Boost package ( 6.95 € Monthly ) and works perfectly on pruned node, they use nvme drives: https://datalix.eu/a/monerotown

Address:
447d29b8j8DiBe8vVCgw6d6DQYmYdULL3PSxoqtdKjAPBaU32okTH622enuhtVHknzJWGBQZZSCLH1fNhgh8wdKDTqG9HgW

View key: e6c7d6dbd9ef0ab5acb21274aa9886940c3f2ba96bb834c7fef2c68d3013a203

A Monero donation fund to rent hashrate
by xenumonero a.k.a anti moonboy

**b*cs marathon is over. They accomplished an 8 and 7 block reorg, but this is nowhere near their claims of having "51% domination". Total reorgs were far less than last Monday. They have one more marathon until their halving, which will impact miner profitability.
It does seem that an ongoing ddos attack has slowed them down (their bagholders are whining about it). Nonetheless, I expect them to go all out on Monday as they are starting to lose the narrative

Let's donate now, not when we are panicking because they are approaching 50%.

Strengthening Monero Amid Attacks – With Xenu of Anti Moonboy News |(MT 359)

TODAY'S 🎙SHOW: Monero’s network is facing coordinated selfish-mining “marathons” by Cubic, causing multi-block reorganizations that disrupt transactions but haven’t led to double-spends. With Cubic controlling an estimated 30–35% of hash power, the attacks combine technical pressure with “weaponized marketing” to boost their own coin. The community is responding by mobilizing CPU miners—especially on decentralized P2Pool—renting hash power during attack windows, and discussing medium-term fixes like fee adjustments, improved mining incentives, and greater decentralization. Broader regulatory headwinds, including high-profile legal cases against privacy tools, add to the urgency. Core consensus is to protect Monero’s tail emission, reject proof-of-stake, and focus on practical, PoW-compatible defenses while reassuring users their funds remain safe.

Watch Here (YouTube)➡️ https://youtube.com/live/VWRMkRyduj8 Listen Here 🎧: https://www.monerotalk.live/monerotalk-359

Coffee & Monero, Go to Gratuitas.org today!

FOLLOW US https://monero.town/u/monerotalk & https://mastodon.social/@monerotalk

Thank you to sponsors, u/cakelabs and u/Stealthex_io as well as u/sunchakr for making these interviews possible! And of course our listeners and supporters for making Monero Talk possible!

Podcasts 🎧 :

iTunes: https://podcasts.apple.com/us/podcast/monero-talk/id1445930212 Spotify: https://open.spotify.com/show/60lQ05X8lcuXv71fhi6hl7

If you enjoy our show please Subscribe, Like, Share, Rate our YouTube Channel & Podcasts. This will help us grow and spread Monero content!

Whenever qubic finds 2 blocks in quick succession, they don't publish them and instead keep building on them in secret as long as they are 2 block ahead of the public chain. When the rest of the network gets close to them and is 1 block away, they publish their longest chain and cause a reorg. Since they don't control 51% of the network if the rest of the miners/pools adopted a "first seen chain -1 n blocks" policy, so kept mining on the first seen chain as long as it's only 1 block shorter than the longest one the qubic strat wouldn't work and all their blocks would get re-orged instead.

Monero's PoW mining pool centralization discussions covered problems, principles, PoW improvements, non-PoW alternatives like Trailing Finality Layer, vulnerability of Nakamoto consensus to rented hashrate and balancing decentralization with security. liberachat

Core principles to uphold in solutions: Privacy, decentralization, censorship resistance, accessibility, and permissionlessness, avoiding complexity, monetary policy integrity. a​rticmine: We have to be careful that we do not create a cure that is far worse than the disease

Improvements to Existing PoW: Tevador's bandwidth-based mining protocol proposal to penalize large pools & encourage decentralization. Sech1's idea of allocating 1% of rewards directly to miners. Short-term mitigations: Renting hashrate, temp raising tx fees as a relay rule.

Non-PoW Consensus Mechanisms: Trailing Finality Layer as an overlay for finality, potentially using PoS for validators, to prevent deep re-orgs and enable faster unlocks. https://xcancel.com/MoneroResearchL/status/1956119998004384085 TEEs withdrawn due to security issues.

Short-Term vs. Long-Term actions and research needs: Immediate: Rent hashrate during spikes; explore PoW tweaks.
Long-term: Research Trailing Finality Layer, PoS failure modes, hardening PoW.
Calls for CCS proposals and literature reviews.

Broad agreement on the urgency of addressing centralization, support for PoW tweaks as realistic short-term steps, rejection of TEEs, and the need for further research. sgp_: I personally think that on the PoW tweak front, tevador's proposal is the most realistic, by far.

kayabanerve: I like tevador's proposal but am concerned about the risk... tevador did respond to this concern though. articmine: I would suggest instead that we focus on hardening our existing POW both at the consensus and node really levels.

Source