I want to start a thread where we discuss the possibility of fostering Pillar-centric communities that are accessible to all participants in the network.
The idea is to encourage pillar-delegate interactions by reducing any friction around accessing communication channels.
The common ground we all have is the network and desktop wallet; why not leverage those to enable bi-directional communication with pillars?
Think of a Telegram or Discord channel:
users read/write messages
users can react to other messages
users can submit/respond to polls
users can have handles/profiles
Pillar-centric social media*, hosted on NoM, accessible via Syrius.
I envision two ways to achieve this objective:
an embedded smart contract could facilitate the tracking of all messages and interactions
a spork will be required
rules can be enforced, such as:
only active delegators have the ability to submit interactions
messages have a character limit
delegates and pillars can craft transactions that contain messages in the data field and send them to the pillar
a spork is not required
may be more challenging to parse the entire interaction history as the network evolves
anyone can submit interactions to a pillar community
Some community members could cache the interactions on their own infrastructure to make these accessible for others to read.
* I think any non-text content will have to be hosted off-chain.
I like the idea of maintaining pillar channels where delegators can communicate with their Pillar (and vice-versa) within Syrius itself. Currently, 0x has a rocketchat for his delegators where they first gotta verify themselves with their delegating address and through signing a message using Syrius. Only the most devout of deeznnuts delegator’s have joined this chat- something that’ll only exacerbate as NoM grows larger.
I like the first option though that sounds like more work for you haha.
For the second alternative- would the crafting of transactions that contain messages require plasma to be fused by the user?
I think this is a really good idea. As we upgrade the network we need a way to communicate and coordinate with Pillars. I like Option 1, but I do think we need to be careful embedding lots of smart contracts. It could increase the attack surface and/or Pillars could get fatigue upgrading the node software. But embedding a SC that helps coordinate activities seems like a good reason to spork. Maybe in the future this could move to the VM layer.
I agree with 0x, I also have some concerns regarding having embedded sc just for Pillars-Delegators communication, while we still have other high priority protocol upgrades that are worth developing and having their own embedded sc.