BlockSkunk now earns an A+ from Mozilla Observatory: 115/100, all 12 tests passed. Trust is not secured by a score. It is earned through work others can check. https://lnkd.in/exH3ZABh
BlockSkunk
Blockchain Services
Sheridan, WY 124 followers
The multi-party system of record. One shared state. Cryptographic proof.
About us
Every multi-party operation runs on fragmented records. When two or more organizations work together, each keeps its own version of who owns what, when it settled, and which rules apply. Reconciliation teams exist to make those versions agree. Compliance teams still scramble to assemble evidence when assessors arrive. A shared database does not fix this. Someone has to own the database. At BlockSkunk, we build the multi-party system of record: shared-record infrastructure every party can cryptographically verify, and no single party controls. Stratum is the infrastructure layer you deploy on. Managed permissioned blockchain, production-ready in weeks, not months. One shared state beneath every party's systems. We operate the network; your teams integrate against open APIs. Six deployment templates cover payment settlement, supply chain provenance, tokenized asset registry, AI agent coordination, assessment records, and multi-party escrow. Arbiter is the record of final authority. A cloud-native validation layer that seals operations into tamper-evident, examination-ready evidence. Assessors verify directly. No reconciliation. No vendor attestation chain. SOC 2, ISO 27001, and NIST controls sealed as they happen. Most enterprises stall because their CISO will not approve infrastructure that lacks verifiable data integrity. We solve that at the protocol level, then compress 18-month enterprise timelines into 14-week integration sprints without sacrificing rigour. We have shipped production systems inside the frameworks: banking infrastructure, supply chain networks, and public-private deployments. We built the systems external assessors examined. The clearest signal is the one no one can alter. We build the neutral record so you can build the network. https://blockskunk.com
- Website
-
https://blockskunk.com/
External link for BlockSkunk
- Industry
- Blockchain Services
- Company size
- 1 employee
- Headquarters
- Sheridan, WY
- Type
- Privately Held
- Founded
- 2025
- Specialties
- blockchain, fintech, enterprise b2b, enterprise software, GRC Software, and enterprise blockchain
Locations
-
Primary
Get directions
30 N Gould St
#65782
Sheridan, WY 82801, US
Employees at BlockSkunk
Updates
-
BlockSkunk now earns an A+ on Security Headers with enforced CSP and key browser protections in place. A grade is not a guarantee. It is one checkable step. The standard we ask of others must begin with us. https://lnkd.in/eqD8BeDP
-
One status. Every gate. Revoke once. A sanctions hit on Friday should stop Monday's settle on every participant not on the one desk that read the email. Static KYB at onboard does not survive ownership change, expiry, or a list hit. Append-only monitoring events do. Expired, failed, or missing facts reject the quote. That is the network kill switch. It is why the product is a sealed fact, not a PDF in a shared drive. Cleared Counterparty. The eligibility fact in front of the quote.
-
-
AI can help us find vulnerabilities faster. We need public infrastructure that helps defenders act on them faster, too. David Kertai's comments for Information Technology and Innovation Foundation on modernizing the National Institute of Standards and Technology (NIST) Vulnerability Database need attention.
AI can help us find vulnerabilities faster. We need public infrastructure that helps defenders act on them faster, too. David Kertai's comments for Information Technology and Innovation Foundation on modernizing the National Institute of Standards and Technology (NIST) Vulnerability Database need attention. This as a governance issue as much as a cybersecurity issue. Teams need timely information they can use and evidence they can defend when someone asks why they acted. This is a necessary shift: automate routine enrichment, ingest structured information from trusted contributors, and preserve human review where judgment matters. 𝗧𝗵𝗿𝗲𝗲 𝗽𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝗲𝘀 𝘀𝘁𝗮𝗻𝗱 𝗼𝘂𝘁: 1. Make uncertainty visible. Tools should distinguish incomplete records from fully reviewed ones. 2. Prioritize practical risk. Severity scores need context about affected systems, reachability, and evidence of exploitation. 3. Keep decisions traceable. AI-assisted recommendations should show their sources, supporting evidence, and changes over time. NVD modernization should be treated as shared infrastructure investment. NIST, vendors, researchers, and enterprise security teams all have a role. The goal should be faster decisions backed by better evidence not simply more automated output. The recommendations go beyond adding AI: ingest structured data from trusted contributors, make incomplete records visible, and keep prioritization decisions traceable. For enterprise, these are practical requirements. Security teams need to know what affects their systems, which evidence supports a decision, and what changed afterward. As the founder of BlockSkunk, this is a principle I bring to our work on Stratum: when multiple organizations contribute to a shared record, the integrity of that record matters. A shared record does not make every claim true. Clear sources, accountable review, and a verifiable history make claims easier to assess with decisions easier to defend. We need to modernize the NVD as shared public infrastructure. Automate the routine work. Preserve human judgment for consequential decisions. Make the evidence usable. AI can increase the pace. Trustworthy records help turn that pace into better decisions. https://lnkd.in/gxZvWdMm #Cybersecurity #AIGovernance #NIST
-
Stablecoins move value. Tokenized assets still need a market that knows who may trade them. Issuing a token answers one question: what asset is represented, and under what offer or disclosure rules? It does not answer whether a particular buyer may acquire it, or whether a seller may transfer it to that buyer. That is the gap between issuance and secondary-market liquidity. For institutions, onboarding can still take days and depend on manual business verification. More token supply cannot fix a process that has not established counterparty eligibility. The practical test comes when a quote is made: can the venue check eligibility then, explain the decision, and carry that decision into execution? MiCA distinguishes white-paper duties from the duties of crypto-asset service providers. Neither substitutes for a clear, current eligibility decision at the point of trade. If eligibility is checked only at onboarding, what happens when the trade arrives?
-
-
$20 Billion in Know Your Bank spend will NOT clear a trade.
$20 billion in KYB spend still will not clear a trade. Juniper Research puts financial-services KYC/KYB systems spend near $20B in 2025, rising toward $30.5B by 2030. That budget covers entity screening, onboarding, and compliance checks. What it does not do is decide whether a counterparty is eligible to trade, settle, or access a venue at the moment of execution. The decision trace timestamped as permission. Verification is not authorization. Clearing needs a current, provable eligibility fact the workflow can read.
-
-
Stablecoins move in seconds. In an era of continuous compliance “We checked last quarter” moves too slow and isn’t an audit trail. The GENIUS Act sets a federal framework. It doesn’t answer the live question before a transaction: is this counterparty still eligible? This article outlines the required evidence behind a decision: who was cleared, for what, under which policy, and until when.
-
$20 billion in KYB spend still will not clear a trade. Juniper Research puts financial-services KYC/KYB systems spend near $20B in 2025, rising toward $30.5B by 2030. That budget covers entity screening, onboarding, and compliance checks. What it does not do is decide whether a counterparty is eligible to trade, settle, or access a venue at the moment of execution. The decision trace timestamped as permission. Verification is not authorization. Clearing needs a current, provable eligibility fact the workflow can read.
-
-
Seventeen U.S. banks are building a tokenized-deposit rail for 2027. That means seventeen institutions need a reliable way to agree who is eligible to participate, clear, and settle on shared rails. The Clearing House selected Quant Network for its On-Chain Money Initiative, with availability targeted for 1H 2027. Reporting described a seventeen-bank group. At that scale, counterparty eligibility stops being an internal ops file and becomes shared market infrastructure. That is the gap BlockSkunk is built to address: one governed counterparty record, visible status changes, and shared verification across authorized participants. If each institution manages that roster in its own spreadsheets, portal flags, and bilateral packs, the market recreates the same onboarding drift it was supposed to remove. That is the job Cleared Counterparty is built for: seal the roster once, govern changes visibly, and let every authorized participant verify the same counterparty status without inventing a new list for every new rail.
-
-
Ninety days and about twenty-two hundred dollars is still what the industry spends, on average, to finish one corporate file.
90 days. $2,274. That is Fenergo's 2024 banking average for a corporate KYC review — cost and calendar. Industry baseline. Not a Cleared Counterparty measurement. The expensive part is rarely the first registry pull. It is the second, third, and fourth review of the same institution at the next venue. If quote volume dwarfs onboard count, meter the sealed subject and the material-change event. Do not meter another KYB seat as if that were the clearing product. At 90 days and $2,274 a review, the second KYB of the same institution is not compliance. It is duplication.
-