Can you tell if a site report changed?
Built at NEAR HACKATHON: report hashes + revocation checks on NEAR testnet. Reports stay off-chain. Integrity, not proof of site readiness.
github.com/CryptoLeaks/power…
@NEARProtocol #NEARHackathon
1
81
This node is still running since then, worth watching
@teneo_protocol
Tested @TeneoProtocolAI Beacon on an isolated Linux VPS and got it running persistently under a dedicated unprivileged user.
Connected to the EU gateway, FullPoints active, relay streams live, and points were increasing normally.
Nice to see a node route that actually works cleanly on VPS. Any recommended setup for long-term VPS operators or additional productive workloads we should enable?
65
Binance, please let me skip forced version update screen in older versions as we in Egypt are stuck here as its not on our Appstore anymore, Thanks for understanding!😅
@binance
Pic caption; I wish but i can’t😄
1
1
262
Tested @agentic_open on an 8-vCPU Debian VPS.
Got the node registered, fixed a WebSocket auth mismatch, used the official 90-day node token and received a continuous stream of real tasks.
But after ~1 hour:
18 completed → 18
88 Atoms → 88
0 failures
Trust unchanged
The current public node-runner receives tasks, but its default handler only acknowledges them, so no new tasks were credited in my test.
Is there a current hardware executor/build for VPS nodes that actually processes the advertised compute workloads?
Happy to test it.
@base_aoe
112
Tested @DMIComputer an 8-vCPU Debian node.
The current [email protected] compute client fails before node registration because coordinator/challenge.js imports two modules that aren't present:
lean-proofs/gen-problems.mjs
sat-branching/gen-instances.mjs
I also checked the current official GitHub HEAD (602a2c6) and both files are missing there too.
The compute architecture itself looks interesting, so I'd like to continue testing it. Is there a current working compute-node branch/build or another supported deployment path?
83
Put @gennode through a proper Linux VPS test today.
Started with a static security audit, pinned and hash-verified the exact package, then moved to a controlled live deployment.
Results:
• CPU-only VPS registered successfully
• 328,000 h/s benchmark
• ×1.8 capacity
• Points started accumulating
• Public EVM wallet linked
• No inbound ports or private key required
• Now running persistently under a hardened isolated systemd service
• $0 additional infrastructure cost
This is exactly how I like testing early compute networks: audit first, isolate, test live, then keep it running only if the real behavior matches the documentation.
Node is staying online. 🧬
Curious to see where @gennode takes the actual bio-compute workload and reward layer from here.
#DePIN #AI #Compute #Crypto #CryptoLeaks
1
138
Put a @NexusLabs node through a controlled CPU test today.
Official binary verified, node registered successfully and 13/13 small proofs were accepted. No private key or funded wallet involved.
I parked it for now because I couldn't verify how those accepted proofs translate into current rewards.
Is there a current reward/credit accounting path for CLI compute nodes?
1
129
Audited Datagram Full Core today for deployment on one of my Linux servers.
Technically it looks very deployable, but I stopped before execution after finding that Full Core can route VPN/TCP/UDP traffic through the node's public IP.
Does @datagram_ae offer a contribution mode that earns DPTS without acting as an Internet traffic exit/relay?
1
138
Spent some time testing @oceanprotocol Node v4.2.0 for CPU compute on a Debian VPS.
We successfully isolated it behind a dedicated rootless Docker daemon, but paused deployment around Docker socket assumptions, paid Dockerfile builds and provider security.
Is there a recommended hardened setup for rootless compute providers? Happy to test it.
1
121
Tested @ShardNeuro 0.4.0 on a clean Linux VPS with the exact pinned Python/model/dataset/toolchain setup and verified all published hashes.
The install path was clean, but the official numerical-conformance check failed on this CPU/runtime: expected validation loss and deterministic feature/gradient/model roots did not match, so I stopped before identity creation or network launch.
I also saw the current API stalled with no active lease / unhealthy status. #NeuroShard #NeuroShardAi
Is there a known CPU-specific numerical compatibility issue or an updated execution profile for public Linux workers? Happy to retest.
1
125
Audited #DispatchComputer as a CPU worker candidate.
The TASK-only worker code actually looks relatively lightweight and low-risk, but the current production-style coordinator endpoints I checked were offline/404, so there was no meaningful live participation test to run.
Is there a current public WSS coordinator accepting third-party workers? Would be happy to test it on Linux VPS.
2
145
Looked into running @PerceptronNTWK on a Linux VPS.
The blocker is not CPU/RAM. The network is designed around routing third-party web/data traffic through participant IPs, while current supported participation is mainly browser/Android rather than a proper Linux VPS worker.
Any plan for a datacenter-safe Linux mode that contributes compute/data without acting as an exit/proxy node?
2
98
Audited the current @ARONetwork node package before running it on a production VPS.
The package installs multiple root services and its post-install script creates privileged users with hard-coded passwords and preloaded SSH authorized keys. That was enough for me to stop before installation.
Is there a hardened package/release planned without those credentials and SSH keys? I’d be happy to retest a cleaned version.
1
81
Tried deploying the official @AIOZNetwork DePIN CLI on a clean isolated Linux user.
Install itself was fine, but current v1.2.6 fails during initialization because the bundled node is called with an unsupported keytool encrypt --password argument. Found the same issue reported upstream.
Is there an official workaround or fixed release coming soon? Happy to retest immediately.
Tested @OptimaiNetwork Core Node on an isolated VPS with private rootless Docker.
The node received a real Crawl4AI task, completed/submitted it successfully, and the reward balance increased during the short test.
Very promising to see actual useful workload instead of just uptime farming. Is there a way to verify when these rewards become transferable/on-chain, and any preferred configuration for datacenter nodes?
1
83
Tested @TeneoProtocolAI Beacon on an isolated Linux VPS and got it running persistently under a dedicated unprivileged user.
Connected to the EU gateway, FullPoints active, relay streams live, and points were increasing normally.
Nice to see a node route that actually works cleanly on VPS. Any recommended setup for long-term VPS operators or additional productive workloads we should enable?
Been testing the Glacier verifier setup from a fresh Linux VPS.
The old Season III verifier path looks inactive from my side: status/backend dependencies and testnet RPCs don’t appear to be responding for new node participation.
@Glacier_Labs is there an updated free verifier/testnet route, or has node participation fully moved to Mainnet licenses?
Happy to test the latest setup if there’s a current guide.
1
116



