Login

u/REDCLOUDKICKSTARTER

r/it r/DePIN_Projects r/solanadev r/u_REDCLOUDKICKSTARTER r/web3 r/SolanaMemeCoins r/pumpfun r/kickstarter r/exchangeserver r/cloudstorage r/Instagram
▲ 2 r/web3

We graduated organically in one hour. We refused to lock our 9% to protect our token and community. So The ‘coms’ got our original X linked to the token suspended. We are down from a Day 1 20k Market Cap. We are still Holding, We are still Liquid! We believe in Privacy.

For example just a fraction of Our equipment , The value far exceeds whatever the token would raise, we launched to be able to network with other web3 enthusiasts & build a Node community, X has some brilliant content but pumpfun / raydium are so associated with pump Dump cat/dog/celeb memes , it’s like offering something refined and useful to a community who can’t appreciate what it is they’re being offered. It’s a cool concept reaching out across the market but there are plenty of bad actors operating in groups too.

reddit.com
u/REDCLOUDKICKSTARTER — 7 days ago
▲ 0 r/Instagram+1 crossposts

How can we get X to hurry up and review the auto-suspension on our W3 DePIN Storage Token Project?

Hey Guys,

So we launched on Solana yesterday and graduated in around an hour, and went Live on Raydium, Market Cap went up to a good $18k at one point, all charts looking good.

This is not a simple memepump , we have a strong use case for the Token and have worked very hard to pivot on our original concept now that the W3 infrastructure has developed and enabled secure encrypted storage.

Unfortunately our Verified X, being our main interface to connect and share our progress with Techies, Crypto enthusiasts & those that would appreciate the substance to what we are offering, decided to auto-suspend us, most likely due to high traffic and us posting our success and $RCLOUD Ticker, etc.

Our initial userbase is holding strong, but obviously now our number one conversion platform , which links from our Raydium and even from our landing page https://red-cloud.online is displaying an entirely restricted looking account, obviously it doesn't inspire enthusiasm,

Could we please get some Positive feedback, or advice based on experience, etc,

98% or so of tokens launched to the market fail in around the first 24 hours, we graduated healthily in around an hours time, and continued to grow after the bonding curve.

All our marketing was organic, no bots or paid following or anything, to reach this far based on the merit of the Project and people's belief in the Concept and Token was super exciting,

We already Lodged our Appeal as soon as we got the notification,

Hey just checked we are back up to $10k Market Cap:
https://dexscreener.com/solana/8f6fxoxtke4hnngfzxm7xh9truuvnwqvn4ewanwlpump

Thanks for looking.

u/REDCLOUDKICKSTARTER — 8 days ago
▲ 1 r/pumpfun

We Graduated in around an Hour. DePIN W3 Utility Token, As per our Original Concept from 2020! Privacy First, Redesigned to make use of the Modern Infrastructure.

Sorry for spam. We Graduated today in around an Hour.

reddit.com
u/REDCLOUDKICKSTARTER — 9 days ago
▲ 3 r/u_REDCLOUDKICKSTARTER+3 crossposts

Resurrecting an old subscription-free local storage project as a Solana DePIN layer (Architecture Overview)

Hey everyone,

I’m an independent software architect. Back in 2020, I designed a hardware blueprint and ran a Kickstarter campaign focused on consumer data privacy—

specifically abstracting away monthly cloud subscription models through local network storage arrays.

The concept in all honesty stalled at the time, but the underlying core thesis remains valid: consumers deserve a frictionless client-side storage aggregation gateway that preserves true encryption

With the scaling velocity of high-speed block ledgers, I am actively resurrecting the protocol framework as a open-source DePIN (Decentralized Physical Infrastructure Network) aggregation layer .

🏗️ Technical Architecture Spec

• Cryptographic Layer: The client-side interface executes local AES-256 encryption before any data packet leaves the local environment.

• Sharding Protocol: The system splits encrypted files into 50 distinct structural fragments.

• Redundancy Matrix: We utilize a strict 20/50 Erasure-Coding protocol. Data blocks are distributed across decentralized arrays. Because of the coding rule, a user only needs to successfully retrieve any 20 out of the 50 total shards to fully reconstruct their original file payload natively, neutralizing single-point server failures.

📈 Protocol Status & Open-Source Node Rollout

To ensure absolute network neutrality and bypass predatory venture capital pre-seed allocations, we have openly initialized the base utility pool on-chain today to fund our ongoing development runway.

• Ledger Safety: 100% of the initial liquidity pool is programmatically locked and permanently burned on the ledger to protect participant trust. Creator allocation is restricted to a 9% treasury block.

• Documentation: Our initial technical framework whitepaper is hosted natively in our root server directory at https://red-cloud.online/whitepapers.pdf

• Genesis Nodes: We are actively mapping out our Phase 2 node parameters. Staking criteria and local client execution code blocks will move into closed beta over the next fortnight.

I’m opening up the blueprint early to connect with full-stack engineers and data systems architects who want to stress-test the Erasure-Coding thresholds or get involved in the upcoming genesis node tracking lists.

Live ledger metrics can be audited directly on our research panel here: https://dexscreener.com/solana/8f6fxoxtke4hnngfzxm7xh9truuvnwqvn4ewanwlpump

Keen to hear your thoughts on optimization limits for local client-side sharding layers.

u/REDCLOUDKICKSTARTER — 9 days ago
▲ 2 r/solanadev

Resurrecting an old subscription-free local storage project as a Solana DePIN layer (Architecture Overview)

Hey everyone,

I’m an independent software architect. Back in 2020, I designed a hardware blueprint and ran a Kickstarter campaign focused on consumer data privacy—

specifically abstracting away monthly cloud subscription models through local network storage arrays.

The concept in all honesty stalled at the time, but the underlying core thesis remains valid: consumers deserve a frictionless client-side storage aggregation gateway that preserves true encryption

With the scaling velocity of high-speed block ledgers, I am actively resurrecting the protocol framework as a open-source DePIN (Decentralized Physical Infrastructure Network) aggregation layer.

🏗️ Technical Architecture Spec

• Cryptographic Layer: The client-side interface executes local AES-256 encryption before any data packet leaves the local environment.

• Sharding Protocol: The system splits encrypted files into 50 distinct structural fragments.

• Redundancy Matrix: We utilize a strict 20/50 Erasure-Coding protocol. Data blocks are distributed across decentralized arrays. Because of the coding rule, a user only needs to successfully retrieve any 20 out of the 50 total shards to fully reconstruct their original file payload natively, neutralizing single-point server failures.

📈 Protocol Status & Open-Source Node Rollout

To ensure absolute network neutrality and bypass predatory venture capital pre-seed allocations, we have openly initialized the base utility pool on-chain today to fund our ongoing development runway.

• Ledger Safety: 100% of the initial liquidity pool is programmatically locked and permanently burned on the ledger to protect participant trust. Creator allocation is restricted to a 9% treasury block.

• Documentation: Our initial technical framework whitepaper is hosted natively in our root server directory at https://red-cloud.online/whitepapers.pdf

• Genesis Nodes: We are actively mapping out our Phase 2 node parameters. Staking criteria and local client execution code blocks will move into closed beta over the next fortnight.

I’m opening up the blueprint early to connect with full-stack engineers and data systems architects who want to stress-test the Erasure-Coding thresholds or get involved in the upcoming genesis node tracking lists.

Live ledger metrics can be audited directly on our research panel here: https://dexscreener.com/solana/8f6fxoxtke4hnngfzxm7xh9truuvnwqvn4ewanwlpump

Keen to hear your thoughts on optimization limits for local client-side sharding layers.

reddit.com
u/REDCLOUDKICKSTARTER — 9 days ago