[DISCUSSION] Solana Intiatives: Solana Spam Handling Logic (SSHL) & Reputation

1. Proposal Purpose:

Discuss and initiate brainstorming and writing for submission to Solana Community or Hackathon. The write up below is a draft of content to consider adding to any submissions or work shared and refined to extract the most useful and pertinent content for the sake of simplicity.

Grape DAO has discussed numerous ideas, not presented here yet, but have been communicated via Discord, X, articles, prior proposals & inherently implied in DAO Governance reputation, participation & rewards models.

TOPIC: Solana Spam Handling Logic (SSHL)

2. Grape Proposal Overview:

Grape will combine efforts to help derive, support, or address ecosystem challenges to help recommend, advise, propose, contribute or critique solutions in a collaborative manner.


The concept of abusive or adversarial messages in the form of intentional network resources spam, spoofing, phishing, flooding, DDoS, or other forms of undesired network activity in the transmission of messages over a network has been a challenge faced by open protocols for years, encouraging the adoption of methodologies to address these each challenge.

Over time, an open system that aims to remain censorship resistant must consider the application of mechanisms to " throttle systematic abuse of un-metered internet resources such as email, and anonymous remailers", as these concepts ignited the crypto revolution with concepts like Adam Back’s Hashcash, one of the foundational concepts leading to the creation of Bitcoin. Thus, there must first be a framework to acknowledge and identify what must be defined, designed, deployed, or declined.

Potential Framework:

  1. Technical Standards (I.e. IETF RFC specs and org notes)
  2. Authentication & Encryption (i.e. SPF, DKIM, DMARC, SSL/TLS)
  3. Regulatory Requirements (i.e. Rules & Laws [Digital & Physical])
  4. Decentralized Governance (i.e. Control, Decisions, & Participation)
  5. Funding Cost (i.e. Open Source, Apps, SaaS, or Hybrid)
  6. Research on Impact (i.e. Pre/Post Feature Deployment Analyses)
  7. User Experience & QA (i.e. End-to-End Feedback from Users & Projects)

As a preliminary framing of the initiative related to addressing spam in an open ecosystem, Email has evolved over time to handle spam by implementing various user-based and system-based solutions which hinge on or result in the derivation of User Choice, Sender or Brand Reputation, System Technical Standards, or UX features.

A.) User-based solutions:

  1. User Preference Opt-In & Opt-Out mechanisms, to sign-up or sign-off, Globally, by Sender, by Publisher, by Brand, or per Message. Requires ecosystem participants honoring opt-in rules, and, opt-out unsubscribe suppression lists.
  2. Email Filter: Scan incoming messages and sort them into different folders based on their spam score. Scan Images, URLs, Links, and File Extensions.
  3. Reporting Spam: Users can submit complaints or signals to a provider or the spam filter service to help them improve their detection algorithms. (CSRF!)
  4. Avoiding opening or responding to spam messages: Prevent malware infection or identity theft.
  5. Disposable Addresses: Unique addresses for signing up to newsletters or online services that might sell or leak personal information.
  6. Change email settings: Block images, links, or attachments from unknown senders or domains.
  7. Real-Time Statistics & Metrics: Combining data from User & System based signals to determine mathematical, Bayesian, or other statistical algorithms to determine spam.

B.) System-based solutions:

  1. Artificial Intelligence and Machine Learning: Analyze the behavior, content, and context of email messages and identify anomalies or patterns that indicate spam.
  2. Sandboxing: Isolate and test suspicious email attachments or links in a virtual environment before allowing them to reach the user’s inbox.
  3. Encryption and Authentication: Protect email messages from being intercepted, modified, or spoofed by malicious actors.
  4. Blacklists and Whitelists: Block or allow email messages from specific senders or domains based on their reputation or trustworthiness.
  5. Spam Traps: Lure and catch spammers by using fake email addresses or domains that are not used for legitimate communication.
  6. Spam Authorities: 3rd Party Groups dedicated to the collection, reporting, status/state changes of resources used in message transmission. These “authorities” are separate from the network providers and ISPs.

In a decentralized system, there are many challenges to ensure it remains decentralized and true to the integrity of the properties that maintain its distributed control.

Advocating for any implementation must heed the cautionary tales of predecessor technologies that may have already succumbed to the pitfalls of censored systems, centralized solutions, or merely the tendency for issues to evolve from chaos to overtly simplified central structures:

  1. untiedbear & Arximedis (Brainstorm)
  2. TinyMCE Spam Checklist: How to bypass spam filtering: the ultimate checklist | TinyMCE | TinyMCE
  3. 7 Best Email Security Software & Tools. 7 Best Email Security Software & Tools.
  4. Best Email Spam Filter Services to Stop Junk in 2024. Best Email Spam Filter Services to Stop Junk in 2024.
  5. How To Get Less Spam in Your Email | Consumer Advice. How To Get Less Spam in Your Email | Consumer Advice.
  6. The Top 5 Email Spam Filtering Solutions in 2023 - MUO. https://www.makeuseof.com/top-email-spam-filtering-solutions/.
  7. The Top Email Spam Filtering Solutions | Expert Insights. https://expertinsights.com/insights/the-top-email-anti-spam-filtering-solutions/.
  8. https://www.getastra.com/blog/knowledge-base/best-spam-filters-for-emails/.

3. Stakeholders

GRAPE DAO Community Members

4. Costs/Resource Requirements:

Contributions will be monitored and rewarded by Grape and/or Hackathon winnings