SPK Network: The Final Push
Shipping the SPK Stack on Hive — DHF Proposal for Finalization and Launch
TL;DR: We are requesting back payment for work completed on SPK Network. To date, we have test releases of Oratr Desktop App, Proof-of-Access, Trole, and Honeycomb v2 with HoneyGraph. Together they unlock arbitrary file upload, end‑to‑end encrypted storage, a CDN for IPFS content with instant access to the storage provider, and an arbitrary service registration/indexing layer—plus full L2 smart‑contract capabilities. The work is largely done. With DHF support, we can productionize, document, and operate this stack so it doesn’t drift into abandonware and instead becomes a durable public good for Hive.
Why this matters to Hive
- Durable storage + delivery: Native IPFS upload paths, integrity guarantees (Proof of Access), and a CDN layer for fast reads.
- Private built in: End‑to‑end encrypted storage for user data and app payloads.
- Composable services: Register, discover, and index arbitrary services on top of Hive via SPK.
- Programmable L2: Honeycomb v2 + HoneyGraph provide a robust L2 execution and data plane (tokens, NFTs, PoB, contracts, real‑time APIs).
- Unlocks new apps: Media apps, collaborative tools, drive‑like experiences, data marketplaces, and dApps that need low‑latency reads with verifiable persistence.
What’s already built (test releases)
- Oratr: End User SPK Network Desktop App. Mac Windows and Linux. Earn just for keeping your computer online. Includes internal IPFS node or connection to an external IPFS node like the IPFS Desktop App.
ipfs-hls-player: An all in one video-js player solution for upgrading video playback to support HLS with CID playlists to support direct IPFS links. Transcode videos to HLS locally in browser at dlux-io, or use the Oratr app.
Proof of Access: A decentralized IPFS file checker that verifies content availability using SPK proofs, aligning incentives with persistence.
spk-js: The portable SPK Network interface, allowing any Hive front-end, or JavaScript environment to interact with SPK Network.
Trole: The Server suite of SPK Network, allowing uploads from anywhere, and running the DPoS PoA Validation software.
Honeycomb v2 + HoneyGraph: Layer‑2 services, smart contract platform, token/NFT/PoB primitives, and a graph‑indexed data plane with real‑time queries.
CDN + dApp hosting (dapp-server): SEO metadata, IPFS fetching, and safe app isolation via custom subdomains to mitigate XSS, enabling a proper content delivery network for apps and media.
Collectively, these components form a cohesive stack that upgrades Hive’s app surface from “content and keys” to “content, compute, storage, and services.”
Capabilities this unlocks
- Arbitrary file upload (direct and managed paths)
- End‑to‑end encrypted file storage (private data, shared spaces)
- CDN‑backed distribution for IPFS media and dApps
- Service registration and indexing (discoverable, queryable services)
- L2 smart contracts and token mechanics via Honeycomb/HoneyGraph
- Real‑time subscriptions and graph queries for dApp UX
Why DHF support now
The heavy lifting is complete. What’s left is production hardening, documentation, operations, and long‑term stewardship. Without DHF support, this near‑finished stack risks becoming abandonware—wasting a unique opportunity to materially expand what can be built on Hive.
What we will deliver with DHF funding
- Security & resilience: End‑to‑end review, threat modeling, hardening, and backup/restore drills; proactive monitoring and SLOs.
- Developer experience: Comprehensive docs, quickstarts, example apps, SDK polish, and CI templates; reproducible test/dev setups.
- Governance & process: Clear policies for upgrades, change management, and deprecation; public roadmaps and changelogs.
- Ongoing maintenance: Triage, bug fixes, minor features, dependency hygiene, and transparent weekly reporting.
Proposed scope, timeline, and budget
We propose a focused 30‑day window to finalize, launch, and transition into steady‑state operations.
Request: 10,000 HBD/day for 30 days (total 300,000 HBD) as a one‑time catch‑up for unpaid labors, and to carry the project through testing and wide release.
Financial context: Our last honeycomb proposal fell behind, resulting in roughly 350 HBD/day out‑of‑pocket for 5–6 months to labor and keep infrastructure online.
- The SPK Network proposal has been unfunded for ~18 months (originally ~5,500 HBD/month to @disregardfiat), creating a maintenance and delivery backlog across ingest, PoA, and DX.
- Despite numerous contributions, @markegiles has never directly been paid for his consistent work on SPK Network.
Payments
- @disregardfiat payments information:
- ~$54,843 For SPK Network in total
- 42 months @ $5,500 would be ~$231,000
- Work could have been faster with the right help. But that also would have cost.
- ~$42,000 For Honeycomb this FY
- Out of $66,000
- ~$54,843 For SPK Network in total
- @markegiles payments received:
- $0 For SPK Network
- ~$31,500 For Honeycomb this FY
- Out of $49,500
This one‑time catch‑up aligns funding with work already delivered and de‑risks the GA launch without committing the DHF beyond the 30‑day window.
If we recoup prior losses during this window, we will continue the project through release and return after release for a maintenance proposal, or utilize a proposal system built in to SPK Network.
Milestones and acceptance criteria
- M1 — Rolling documentation and recipes: Continued release of documentation, quickstarts, and use‑case recipes covering migrating Hive image servers to SPK Network; upload → encryption → delivery; service registration; and common dApp patterns. Acceptance: new docs/recipes published weekly; coverage of all core flows required for GA.
- M2 — Bug triage and stabilization: Respond to bug reports, maintain a public ToDo and release notes, drive backlog toward release candidate. Acceptance: published triage policy, weekly burn‑down report, and shrinking open‑bug trend.
- M3 — Tokenomics & PoA lottery finalization: Test and finalize release tokenomic parameters and PoA lottery mechanics. Acceptance: published parameter spec, community review sign‑off, and configured values in release candidate.
- M4 — DEX integration testing: Exercise DEX paths end‑to‑end; publish test results and gating criteria. Acceptance: public test report, identified fixes (if any), and pass/fail decision logged for GA.
- M5 — Conditional: AMM DEX pilot (≥200k/300k collected): If funding surpasses 200k HBD during the window, deliver an AMM DEX pilot. Acceptance: testnet pools live with swap/LP flows, basic audits, and migration plan to mainnet.
- M6 — Release candidate → GA: Community selection of release candidate and cut to production versions. Acceptance: tagged RC, GA tag/date announced, release notes, and hardening checklist completed.
- M7 — Distribution & end‑user apps: Add end‑user apps to standard pipelines (major app stores, apt, etc.) for supported environments. Acceptance: public listing URLs and install commands, CI pipelines for repeatable releases.
Each milestone will ship with change notes, runnable examples, and measurable success criteria.
How to review and test today
- Functional test network: dlux.io
- Service endpoints:
- Proof of Access: poa.dlux.io
- SPK Upload/API (Trole): ipfs.dlux.io
- CDN delivery:
ipfs.dlux.iosubdomains &honeygraph.dlux.ioAPIs
- Core repositories:
- HoneyGraph: github.com/disregardfiat/honeygraph
- Honeycomb SPKCC: github.com/spknetwork/honeycomb-spkcc
- Trole: github.com/spknetwork/trole
- Proof of Access: github.com/spknetwork/proofofaccess
- Oratr: github.com/spknetwork/oratr
- spk-js: github.com/disregardfiat/spk-js
- ipfs-hls-player: github.com/markegiles/ipfs-hls-player
Accountability and transparency
- Weekly public updates (progress, incidents, next steps), and reporting to swarm of swarms.
- Open issue tracker and discussed priorities via github(per repo) & trelo(per repo + larger scopes)
- Post‑mortems for incidents and security events
Success metrics
- SPK Network comes online & incentivization works with the DEXs
- HoneyComb is generally released with the same system on chain, system level smart contracts.
- Token & NFT builders utilize SPK Network as a seed storage for HoneyComb comunnities.
Call to action
If you want Hive to ship encrypted storage, robust CDN delivery, a service registry, and L2 smart contracts—backed by components that already exist—please support this DHF proposal.
- Comment with feedback and requested adjustments to scope/timelines.
- Signal support once the proposal is live.
- Try the test releases and open issues with your findings.
With DHF support, we can take this stack the last mile through testing as a long‑term public good for Hive, rather than letting near‑finished work go to waste. Every feature discussed here is currently working, only integration testing and wide release remains.
As you can see, if having a storage and application layer on Hive can boost the chain growth by even 10% APY this DHF proposal will more than pay for itself.
You can play with proposal budget projections at dlux.io
Supported thanks for the hard work keep it up! !PIZZA !LOL
lolztoken.com
He was charged with battery
Credit: reddit
@disregardfiat, I sent you an $LOLZ on behalf of sirsmokesalot96
(3/6)
NEW: Join LOLZ's Daily Earn and Burn Contest and win $LOLZ
$PIZZA slices delivered:
@sirsmokesalot96(1/15) tipped @disregardfiat
Come get MOONed!
Thanks for all your work on this and for inviting community feedback. It is very often the case that when proposals get funded, the desire of people behind them to integrate community feedback into their work and roadmaps wanes. With this disconnect, community support goes down over time. It feels like with a project of SPK's magnitude, this kind of disconnect has happened, and the community rightly wants to see its priorities addressed. Just my two cents - take it or leave it.
My personal feedback is that I would like to see a more concrete first milestone that will bring a new feature that can be felt by the Hive user. That could be for example the delivery of an image hosting service which frontends can begin using instead of the centralized image servers they use now. In essence, I want to see an SPK feature that becomes fully available, and the deliverable is not simply a release of a software package or documentation but for the average Hive user to be able to use this feature.
Feel free to download the desktop app... and use the CDN to host images.
https://honeygraph.dlux.io/fs/disregardfiat/NFTs/Resources/bees-set-featured.pngAs I said, every feature mentioned here is written and testable.
I would like to use a frontend to upload images to SPK network. This seems like the most common use case. What is needed for frontends to be able to offer this feature?
We have spk-js that has been built with this in mind, so any front end can be able to upload and view files with little effort.
You can do this now at dlux.io drive section. (Though it's not running on spk-js yet)
Great. So can frontends implement this now?
We are trying to implement it into 3Speak with little success so far. Im sure Disregard will help @kesolink to make something of this in the new release, but as of yet, we aren't able to implement it
I would love to get this project into GA! That what this proposal is for.
I will not be engaging in unpaid, platform specific work though. If you'd like to bring this project to fruition and integration, I'd recommend re-blogging this post, voting for and advocating for this proposal.
This comment probably is an accurate reflection of how the community feels. Hope we can find a way to progress
https://hive.blog/dhf/@borislavzlatanov/re-disregardfiat-t20ew4
The reply to that comment demonstrates the feature. We have demonstrable features covering the White Paper and half the phase 2 work as well.
You were the PM for this project, my last update doesn't have your vote, reblog, or engagement, that trend continues. If the community doesn't understand where we are that is on you. I'm here pushing for completion, doing the community outreach, trying to secure funding, AND have written a tremendous amount of code... and the major opposition appears to be you.
SPKs codebase is larger than Hive - 75494, with Hive-js - 18037, and HAF - 163003 ( 256,534 Lines - Methodology
git ls-files | xargs wc -l) in size... Yes, it took awhile.If the community wants further progress, they can vote for it... If not I'll have to find another way to pay the bills.
I’m not the PM. I’m just the idiot trying to make sure the community gets what it paid for.
If this tech is not implemented into an app like 3Speak and no other apps use it, then its probaboy nit finsihed and should nit be paid for. I don’t understand why u think anything has been built if no apps use this tech and no apps can implement it. Once a few apps have integrated it (which should be easy if u built this tech out as u say)
The community seems to have been funding vaporware for the last 3.5 years, 2.5 of which u have been building (not 4 as u state above)
I’d suggest revising ur request for funding down to about 40k after it’s implemented into a couple of dapps
I’d say that would be a fair moment for the community to opt into funding u again.
There is nothing wrong with getting external funding / work and getting this system to a place where it’s implemented into several apps as a part time thing or outside a normal job hours
For those not in the loop @starkerz was the custodian of the spkproposal.
It's very first payment is here - September 10th 2021. Which just might be 4 years ago... Sorry for missing a week.
And the first payout to me is here November 2, 2021.
With major work starting here March 2nd 2022
It had payouts in the following amounts(Done by hand, sorry if there are errors):
nathansenn: $47,012.11
sisygoboom: $5,227
noakmilo: $950
vaultec: $63,307
sagarkothari88 : $28,639.31
disregardfiat: $52,513.52
adesojisouljay : $9,033
kesolink: $3,400
igormumba: $20,210
juneroy1: $5,000
psorigins: $5,050
deathwing: $350
eddiespino: $700
sqhell: $7,850
peerplays: $4,500
pbsa: $8,500
vicypher: $5,500
with additions from
threespeakfund: -$4,117
curatorhulk: -$200
starkerz: -$300
theycallmedan: -$100
speak.delegation: -$7,109.91
Many of these payouts were to intermediate steps, website creation, graphics, copy and proof reading, and dead end paths... and that's just how it is.
@nathansenn's contributions to this project were valued at roughly $10 per line of code. Shown by payments from spkproposal and the contributors pages of the above listed projects. $10 per LoC is a very reasonable payment in this scope of work and sector.
However, across the project I have over 200,000 LoC. Pricing me at roughly $0.25 (and roughly $1 if you include the HoneyComb Proposals) per line of code, among other factors.
But there does seem to be $100,000 in outflows that didn't benefit SPK Network at all. Were you using the SPK proposal to fund development of 3speak.tv? I'm just an idiot trying to make sure the community is getting what it paid for.
@rollie1212 recently installed the whole server side suite.
spk-js is on NPM
It's used in the downloadable desktop application Oratr - Releases
We even built a IPFS HLS transcoder, and NPM hls player --- player - in -action
So let's recap... You lost a year, have no idea how to value software development at best, demand to have me work to help integrate the test network into 3speak.tv, and think writing: a claim drop, storage contracts, 3 DEXs, Upload and CDN microservices, A desktop app, an NPM package, rewriting proof of access, a graphQL layer, should be paid roughly the same as working the same amount of time in an In-N-Out Burger.
Installed
For now have no idea why I did that :))))
You were instrumental in making sure our binaries were properly included in the install script. I'm also questioning why I built it though
)
No, I’m paying someone else to implement SPK network into 3Speak out of my own pocket. I just want u to help guide him to do it since u understand the tech. This is almost zero effort for you to do
After multiple attempts to reach out to u, and no responses, we aren’t able to integrate this tech into 3Speak.
My view is that it is fair that once some dapps have integrated the tech u built and their users are getting paid to store content, then I’d be pro supporting u to get more funding But not 300k
I turned chatGPT loose in my dev folder:
What would you estimate to be the development cost of this suite of microservice?High-level estimate
Person-months by service (engineering only)
dapp-server (IPFS CDN, SEO metadata, subdomain isolation): 6–10 PM
dlux-iov (Vue PWA, wallet flows, offline, UX polish): 12–18 PM
docker-data (block processing, DB, ETL, APIs): 8–12 PM
honeycomb-spkcc (L2 contracts, APIs, tokens/NFTs, storage): 16–24 PM (+ audit)
presence (read-replica APIs, STUN/TURN, scaling): 4–6 PM
proofofaccess (IPFS proof validation, schedulers, consensus hooks): 8–12 PM
trole (SPK API, signature checks, upload orchestration, node mgmt): 10–14 PM
dlux-docs (site + service docs/runbooks): 2–4 PM
Subtotal engineering: 66–100 PM
Add TDD/QA automation hardening: +15–25% → ~76–125 PM
Add DevSecOps/SRE (platform, CI/CD, IaC, observability): +15% parallelized
Product/PM/Design: ~10–15% parallelized
Practical team shape and timeline
Budget ranges (all-in engineering, excluding infra)
Additional line items
If you’re hardening/extending the existing repos instead of greenfield
Key cost drivers to watch
docker-data,trole,proofofaccess.honeycomb-spkcc.dlux-iov.presence(TURN egress can spike costs).13 to 22K person hours... this is sadly accurate.
Yes but no one is using ur stuff and when people ask how to implement it u ignore them. Once u stop ignoring the people who want to implement what u have apparently built and help them implement it, u may be able to say that u built all the stuff as others can verify its working. If its not working, the community should not pay u any money.
Maybe u should just get it working in someone’s app and then we can all be happy that u did the work u say u did. Lines of code don’t matter. What matters is if ur tech is operating in several hive dapps. Then u can talk about getting paid.
Asking for 300k at the last minute when the tech is apparently ready to implement and there are people ready to implement the tech but ur ignoring their requeste for assistance in implementation until u get paid 300k is a disingenuous way to go about getting funded on hive.
I ignore the person who withheld payment to me for over a year while asking for phase 2 work, while not lifting a finger to even reblog updates.
At least one of us looks like an asshole I'm sure. I wonder if it's the guy with all the cards or all the receipts.
At this point i think u arent capable to finish this work. U have been saying it will be “ready next week” since Hive fest 2023.
Once u can finish the work and a couple hive apps are running ur storage tech that maybe u kindly helped them with implementation, u should be getting paid a bit more. But I don’t think u will as I don’t think what u built works and I won’t be voting for any more money to go ur way until you actually show an existing hive dapp with ur storage system (which u claim Is finished) running in it
Well at least you won't be asking me to rebuild: The upload mechanism, so that files can be sidelined and servable before their entry into IPFS. Having me rebuild the tokenomics and add a new dex based on the feedback of 1 person. Or any of the minutiae that makes you a better "idiot" than a PM.
And you remembered your missing year! Getting better already.
Software is hard... I believe the Hardfork for Hive is also over a year late now. I bet the core team isn't worried about how to pay the bills.
Congratulations @disregardfiat! You received a personal badge!
You can view your badges on your board and compare yourself to others in the Ranking
Check out our last posts:
It is sad to see one of the hardest working HIVE developers struggling to get funding. It is no surprises HIVE has been stagnating. I wish to see a change of the current state of things and those with stake start backing gems like you to do great things. I'm highly disappointing by how the best and most promising projects we have are getting treated.
Best of Luck!
Hello disregardfiat!
It's nice to let you know that your article won 🥉 place.
Your post is among the best articles voted 7 days ago by the @hive-lu | King Lucoin Curator by deepresearch
You and your curator receive 0.0001 Lu (Lucoin) investment token and a 4.69% share of the reward from Daily Report 776. Additionally, you can also receive a unique LUBROWN token for taking 3rd place. All you need to do is reblog this report of the day with your winnings.
Buy Lu on the Hive-Engine exchange | World of Lu created by @szejq
STOPor to resume write a wordSTART