After the CCS hack, fluffypony proposes breaking up the Monero Core team:
"Currently the Monero Core Team is responsible for a number of things that are critical to Monero, and as a result there is a great level of trust implicit in them. For instance, a malicious Monero Core Team member could hijack the domain, and serve up malicious Monero downloads right after a new release. No matter how quickly this is detected, there will be many affected downloads, and could cause massive financial and privacy-related network damage. The recent CSS wallet incident is also an example of risks that the Core Team presents.
Additionally, this has been a thankless job that the Core Team has taken on (for no compensation), although even if there were compensation and constant praise it would still be a centralising force that we should try and eviscerate.
My suggestion, and I encourage us to use this thread to iterate on it in public, is to break the Core Team up into 6 self-assembling workgroups. This is not a complicated exercise, apart from the community coming to consensus as to who should form part of the workgroups. I would suggest we aim for a January 1st, 2025, cutover date for this."
https://github.com/monero-project/meta/issues/921
#monero
#archer_crypto
archerships / Archer Ships
npub1sx…ak49e
2023-11-05 23:09:14
Author Public Key
npub1sx7d85ccx0pc2zk99t8glywc9hsy96fj67a3lgxmxew7h35dwp8shak49ePublished at
2023-11-05 23:09:14Event JSON
{
"id": "c19011b3fae30d82fc1ac562eb91aca0b8100017087ab316c96f23378ee38acc",
"pubkey": "81bcd3d31833c3850ac52ace8f91d82de042e932d7bb1fa0db365debc68d704f",
"created_at": 1699225754,
"kind": 1,
"tags": [
[
"t",
"monero"
],
[
"t",
"archer_crypto"
]
],
"content": "After the CCS hack, fluffypony proposes breaking up the Monero Core team:\n\n\"Currently the Monero Core Team is responsible for a number of things that are critical to Monero, and as a result there is a great level of trust implicit in them. For instance, a malicious Monero Core Team member could hijack the domain, and serve up malicious Monero downloads right after a new release. No matter how quickly this is detected, there will be many affected downloads, and could cause massive financial and privacy-related network damage. The recent CSS wallet incident is also an example of risks that the Core Team presents.\n\nAdditionally, this has been a thankless job that the Core Team has taken on (for no compensation), although even if there were compensation and constant praise it would still be a centralising force that we should try and eviscerate.\n\nMy suggestion, and I encourage us to use this thread to iterate on it in public, is to break the Core Team up into 6 self-assembling workgroups. This is not a complicated exercise, apart from the community coming to consensus as to who should form part of the workgroups. I would suggest we aim for a January 1st, 2025, cutover date for this.\"\n\nhttps://github.com/monero-project/meta/issues/921\n\n#monero\n#archer_crypto",
"sig": "e164a542894eb3469057bc035778aaac31db6e96b9d9fecc104505aee7c3b7fe71d3ce8b3ead5101b3699426c92912beae80ad8a7ceea51554cec65ba615a779"
}