# Web3Sec brand and publishing guide

Version 2.0 · Updated 9 November 2026 · Owner: Raiders

This guide applies the existing Web3Sec identity across digital publishing, presentations, documents and physical production. It is an operator handoff. Preparing artwork or copy does not upload profiles, post announcements, request indexing or manufacture products.

The identity source is [brand.ts](https://github.com/web3sec-news/web3sec/blob/main/src/content/brand.ts); the public guide content is [brand-guidelines.ts](https://github.com/web3sec-news/web3sec/blob/main/src/content/brand-guidelines.ts). Use [manifest.json](https://www.web3sec.news/brand/manifest.json) to identify actual exports and [contact-sheet.png](https://www.web3sec.news/brand/contact-sheet.png) to compare them. Production recommendations need an approved proof at the final size.

## 1. Identity and positioning

**Web3Sec is an independent security practice and research publication led by its founder, Raiders.** The work connects system behavior, operational authority and technical evidence with decisions that engineers and leadership can act on.

Write **Web3Sec** in running text and **Raiders** for the person. Use **Web3Sec.News** when quoting an external contributor credit or the publication’s historical name. The dot drawn in the wordmark is an artwork detail, not a requirement to add punctuation to every mention. Use `https://www.web3sec.news/` as the canonical website.

The eight engagement areas are crypto operational security; smart contract security; web, API and full-stack pentesting; mobile app security testing; incident readiness and scoped response; AI and supply-chain security; technical writing and research; and security strategy and technical GTM advisory. Select the relevant area for the audience. A treasury owner needs signing and recovery controls; a mobile engineer needs the app, device and API boundary. Neither needs eight service names on every cover.

**Primary tagline:** Independent security. Clear decisions.

Contextual alternatives: “Evidence for the decisions that matter.” or “Review the paths that control your system.” Use one line at a time. A tagline identifies the approach; a service description explains the work and an engagement scope defines its limits.

Use “Led by Raiders” when clarifying the relationship. Do not imply a large staff, continuous response coverage or unconfirmed specialist availability. Commercial relationships must not determine editorial conclusions.

## 2. Mark, lockups and geometry

The symbol is a two-by-two arrangement of four equal squares: three in the principal color and the lower-right square in the accent. A useful visual reading is attention to one part of a connected system. Do not present that interpretation as a founding story or assign the squares to fixed services, pillars or certifications.

The source uses a 64-unit artboard. Painted geometry runs from 12 to 52 on each axis: **40 units overall**, made from **16-unit tiles** separated by an **8-unit gap**. Measure spacing and minimum size from painted artwork, not invisible export bounds.

| Variant | Role |
| --- | --- |
| Horizontal mark and name | Headers, document attribution, signatures and wide applications |
| Stacked mark and name | Centered covers, narrow placements and physical applications |
| Mark alone | Brand avatars, favicons and an already identified context |
| Name-only wordmark | Constrained attribution where a symbol adds clutter |
| Single-color variant | Engraving, embroidery and restricted reproduction |

Use the supplied **production masters**, available as transparent SVG/PNG in all four variants:

| Production master | Export dimensions |
| --- | --- |
| `logo-horizontal-{variant}` | 1800×432 |
| `logo-stacked-{variant}` | 1200×1000 |
| `logo-wordmark-{variant}` — name only | 1600×400 |
| `logo-mark-{variant}` — symbol only | 1000×1000 |

Replace `{variant}` with `ink`, `paper`, `black` or `white`. Ink uses ink and terracotta on a light surface; paper uses paper and peach on ink. Black and white are true one-color artwork. Files are transparent: the variant name describes the artwork, not an included background.

These logo SVGs contain **outlined, font-independent glyphs**. Preserve the supplied native vector shapes; do not retype, substitute a font or redraw the wordmark. Outlined glyphs are solid filled artwork, not an outline-only visual effect. Older `wordmark-ink` and `wordmark-paper` exports remain editable live-font **horizontal lockups**, distinct from the name-only production masters. Keep editable-source and production folders clearly labeled.

Reserve **at least one tile width** of clear space around the painted mark or entire lockup. A tile is 0.4 times the painted mark width: a 40px painted mark needs 16px clear space per side; a 10mm mark needs 4mm. Use the mark component to establish the unit for a lockup. Export padding may contribute; do not count it twice. Increase spacing beside dense text, other identities or a trim edge.

Recommended starting minima are a 24px painted mark digitally or 6mm in print; a 140px/30mm horizontal lockup; and a 100px/24mm stacked lockup. Inspect the name, gaps and accent at actual size. The approved site favicon is a deliberate small-size exception. Coarse embroidery and engraving may require larger artwork.

On light paper use ink with terracotta. On ink use paper with peach. Use true single-color artwork when needed, keeping all four tiles. Do not stretch, rotate, round tiles, change spacing, add shields, apply gradients or shadows, use outline-only restyling or randomly recolor tiles. Keep ornamental grids visibly separate from the logo. Use a quiet solid area when photography would obscure it. Review `logo-clear-space`, `background-pairings` and `logo-usage-examples` SVG/PNG boards for construction and placement.

## 3. Palette and accessibility

The screen master is **sRGB**. CMYK values below are rounded mathematical RGB conversions using a simple black-component formula. They are **not printer profiles, approved press separations, ink recipes or Pantone matches**. Agree substrate, ink, coating and output profile with the producer and approve a physical sample.

| Role | Hex | RGB | Approximate CMYK % |
| --- | --- | --- | --- |
| Primary ink | `#202923` | 32 / 41 / 35 | 22 / 0 / 15 / 84 |
| Primary paper | `#f4f1e9` | 244 / 241 / 233 | 0 / 1 / 5 / 4 |
| Terracotta accent | `#a43e29` | 164 / 62 / 41 | 0 / 62 / 75 / 36 |
| Muted text | `#59615a` | 89 / 97 / 90 | 8 / 0 / 7 / 62 |
| Peach on dark | `#d6906f` | 214 / 144 / 111 | 0 / 33 / 48 / 16 |
| Production white | `#ffffff` | 255 / 255 / 255 | 0 / 0 / 0 / 0 |
| Production black | `#000000` | 0 / 0 / 0 | 0 / 0 / 0 / 100 |

Keep ink and paper dominant. Terracotta marks emphasis and selected actions. Muted is readable secondary text. Peach is the light accent on dark surfaces. White and black are production alternatives. Do not introduce a new accent for each service.

These ratios were calculated from the exact sRGB colors using WCAG relative luminance. Display values are rounded; threshold decisions use underlying values.

| Text / background | Ratio | Ordinary text |
| --- | --- | --- |
| Ink / paper | 13.26:1 | Passes AA |
| Muted / paper | 5.67:1 | Passes AA |
| Terracotta / paper | 5.64:1 | Passes AA |
| Peach / ink | 5.76:1 | Passes AA |
| White / ink | 14.97:1 | Passes AA |
| White / terracotta | 6.36:1 | Passes AA |
| Black / white | 21:1 | Passes AA |
| Terracotta / ink | 2.35:1 | Fails |
| Peach / paper | 2.30:1 | Fails |

[WCAG ordinary text requires 4.5:1; qualifying large text requires 3:1](https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html). Required control cues and meaningful graphics generally need [3:1 against adjacent colors](https://www.w3.org/WAI/WCAG22/Understanding/non-text-contrast.html). Recalculate for opacity, overlays, gradients and images. Palette compliance alone does not establish page accessibility. Pair status, severity and allow/deny colors with words or another cue.

## 4. Typography and layout

Use the native stacks: **Georgia, Times New Roman, serif** for editorial headings; **Arial, Helvetica, sans-serif** for paragraphs, controls and explanatory labels; **Courier New, monospace** for restrained technical metadata. Use supplied wordmark artwork rather than resetting the logo in a similar font.

Start digital paragraphs at 16–18px, line height 1.6–1.75 and roughly 55–75 characters per line. Use one title, a short deck, ordered headings and visible sources. Avoid long uppercase passages, oversized mono text and dense italic paragraphs. Quiet rules and whitespace often separate content better than another bordered container.

For 1200px-wide figures, use at least 18px labels and inspect their actual display size. If a shared figure becomes unreadable, reduce content rather than shrinking everything. For 16:9 slides, start around 36pt titles and 24pt body; check from the intended viewing distance. Review print documents at 100%, including captions and page numbers.

System font names in CSS do not distribute font files. This kit bundles no proprietary font binaries and grants no font redistribution rights. Production logo masters need no installed font; editorial templates and older editable lockups still contain live system-font text. Check font, operating-system and application licenses before embedding or transferring fonts; [Microsoft’s font FAQ](https://learn.microsoft.com/en-us/typography/fonts/font-faq) distinguishes rendered output from font redistribution. Supply a proof PDF/PNG for appearance and editable text where permitted. Fixed vector artwork does not license font redistribution. Inspect editable SVG exports for substitution and changed metrics; never retype an outlined production logo.

## 5. Voice, evidence and credits

Lead with the reader’s question. Name the system, describe its relevant boundary, explain what the evidence establishes and give a practical action. Prefer “Review who can publish the frontend” to “Unlock enterprise-grade protection”; prefer “Retested the stated build” to “Fully secured.” Attach dates and tested versions where they affect interpretation.

Distinguish a reported fact, a demonstrated finding and an inference. Keep incident, disclosure and publication dates separate. Put limitations beside their claims. Avoid “never miss a breach,” “hack-proof,” guaranteed recovery, ranking promises and unqualified coverage of every attack or specialty.

Preserve these specific public attributions:

- **SEAL:** Raiders is credited as author of the [Domain & DNS Security framework](https://frameworks.securityalliance.org/infrastructure/domain-and-dns-security/overview/). This does not establish employment or accredited certification status.
- **MITRE AADAPT:** **Chirag Agrawal, Web3Sec.News** is a named contributor to [Supply Chain Compromise, ADT1195](https://aadapt.mitre.org/techniques/ADT1195/) and [Compromise Software Dependencies and Development Tools, ADT1195.001](https://aadapt.mitre.org/techniques/ADT1195.001/). Call it a technique contribution, not MITRE certification or a generic ATT&CK award.
- **TheDAO Security Fund:** Raiders [announced ETHSecurity Badge selection in April 2026](https://x.com/__Raiders/status/2043883600152801651). Use “ETHSecurity Badge holder” without a researcher ranking. The [transparency record](https://thedao.fund/transparency/) names Web3Sec.News and DigiBastion as funded projects; this does not establish two separate funding rounds or client endorsements.

Use [public work](https://www.web3sec.news/work) for report-specific roles. Collaborative credits stay collaborative. Keep hypothetical findings labeled illustrative. Do not turn confidential work into public case studies or display third-party logos as customers without authorization.

## 6. Copy-ready profiles and links

**One sentence**

> Web3Sec is an independent security practice and research publication led by Raiders, connecting technical evidence with clear decisions.

**X display name:** Web3Sec

**X brand bio — 155 characters**

> Security by Raiders: crypto OpSec, contracts, web/API, mobile, AI/supply chain, incident readiness, technical writing & security/GTM advisory. web3sec.news

**LinkedIn company tagline — 114 characters**

> Crypto OpSec, contract/web/API/mobile testing, AI & supply-chain security, incident readiness, writing & advisory.

**LinkedIn company About**

> Web3Sec is an independent security practice and research publication led by Raiders.
>
> Engagements cover crypto operational security, smart contract security, web/API and full-stack pentesting, mobile app security testing, incident readiness and scoped response, AI and supply-chain security, technical writing and research, and security strategy and technical GTM advisory. Scope, access, availability and specialist needs are agreed for each engagement.
>
> Public contributions include Raiders’ authorship of SEAL’s Domain & DNS Security framework. MITRE AADAPT lists Chirag Agrawal, Web3Sec.News, as a contributor to Supply Chain Compromise (ADT1195) and Compromise Software Dependencies and Development Tools (ADT1195.001). These credits describe specific contributions.
>
> The publication turns primary incident reports and technical documentation into source-linked analysis and practical operating guides. Explore the work at https://www.web3sec.news/ or message Raiders at https://t.me/Raiders0786.

**Raiders personal headline**

> Raiders | Founder, Web3Sec | Crypto OpSec, contract/web/API/mobile security, AI, incident readiness & technical advisory

**Raiders personal About**

> I’m Raiders, founder of Web3Sec. My work connects the code, applications, identities, devices and operational dependencies around crypto systems.
>
> Engagements can cover crypto OpSec, smart contract reviews, web/API and full-stack pentesting, mobile app security, incident readiness and scoped response, AI and supply-chain boundaries, technical writing and research, and security strategy or technical GTM advisory. Each engagement starts with the actual system and decision, then agrees on coverage and evidence.
>
> I’m credited as author of SEAL’s Domain & DNS Security framework. MITRE AADAPT names Chirag Agrawal, Web3Sec.News, as a contributor to ADT1195 and ADT1195.001. I was selected as an ETHSecurity Badge holder by TheDAO Security Fund in April 2026.

| Channel | Confirmed destination | Role |
| --- | --- | --- |
| Website | https://www.web3sec.news/ | Canonical identity, work and research |
| Telegram | https://t.me/Raiders0786 | Preferred first conversation |
| GitHub | https://github.com/Raiders0786 | Public code and portfolio |
| X | https://x.com/__Raiders | Raiders’ personal public profile |
| Newsletter | https://web3secnews.substack.com | Publication and subscription |
| Engagements | https://www.web3sec.news/engagements | Compare scope and outputs |

A short Telegram question is enough; a first message does not require a complete brief. Agree on handling before transferring private source, evidence or customer information. Never ask for seed phrases or private keys. Verify changed channels through an established identity before publishing them.

## 7. Imagery, motion and accessibility

Use visuals to explain a mechanism. A receipt, permission matrix, release layer, response clock or authority ring each answers a different question. Avoid making every article another boxes-and-arrows composition. Keep line weight deliberate, labels limited and illustrative values clearly identified.

Avoid stock hooded hackers, meaningless code, fictional live dashboards, invented loss charts and imagery implying access to a real incident. Generated art may illustrate concepts; it must not impersonate documentary evidence, a client environment, a real portrait or endorsement. Retain editable sources and stable exported images.

The point must survive without animation. Honor reduced-motion preferences, retain a static state and avoid flashing, continuous parallax and decorative loops. Content remains available when scripts or images fail. [W3C’s animation guidance](https://www.w3.org/WAI/WCAG22/Understanding/animation-from-interactions.html) explains user control over nonessential movement.

For informative images, describe the point in alt text; explain complex figures in nearby prose. Decorative images should not repeat surrounding text to screen readers. Use a functional name such as “Web3Sec home” for a linked logo. Keep headings and substantive text outside artwork too. Follow [W3C’s alt-text decision tree](https://www.w3.org/WAI/tutorials/images/decision-tree/), then check keyboard access, focus, zoom and reading order on the page.

## 8. Social exports and uploading

Use PNG uploads and retain SVG vector sources. Paths are under `public/brand/`; verify the manifest before distributing a kit.

| Placement | Export | Size |
| --- | --- | --- |
| Company avatar | `profile-light-400.png` / `profile-dark-400.png` | 400×400 |
| X header | `x-header.png` | 1500×500 |
| Raiders LinkedIn background | `linkedin-personal-cover.png` | 1584×396 |
| LinkedIn company cover | `linkedin-company-cover-1512x256.png` | 1512×256 |
| Larger company-cover alternate | `linkedin-company-cover.png` | 4200×700 |
| Large brand avatar | `profile-light-1024.png` / `profile-dark-1024.png` | 1024×1024 |
| Production logos | `logo-{layout}-{variant}.svg/png` | See production-master table |
| Legacy transparent mark | `mark-ink.svg/png` / `mark-paper.svg/png` | 1024×1024 export |
| Editable horizontal lockup | `wordmark-ink.svg/png` / `wordmark-paper.svg/png` | 1600×360 export |
| Organization identity | `logo-square.svg/png` | 512×512 |
| Site share image | `web3sec-share.svg/png` | 1200×630 |

[X recommends 400×400 profile artwork, 1500×500 headers and a 160-character bio](https://help.x.com/en/managing-your-account/how-to-customize-your-profile). [LinkedIn personal backgrounds are 1584×396, PNG/JPG, up to 8MB](https://www.linkedin.com/help/linkedin/answer/a549049). Keep Raiders’ personal portrait; the mark represents the company rather than the person’s likeness.

[English LinkedIn Page guidance](https://www.linkedin.com/help/linkedin/answer/a570368?lang=en), checked 9 November 2026, specifies a 400×400 logo and 1512×256 cover, PNG/JPEG up to 3MB. Older cached guidance differs, so the 4200×700 alternate remains available. Use the actual Page interface’s specification. Keep essential content away from avatar overlap and edge crops.

Confirm the account, preserve previous assets, upload the mapped export, update matching copy and canonical links, preview desktop/mobile crops, then verify the public view. Record the change. Do not claim a profile or release was updated until that action is complete.

## 9. Reports, slides, signatures and covers

Reports and proposals should show a concrete title, system or scope, author, version and date. Distinguish reviewed artifacts, methods, findings, evidence, limitations and next actions. Use page numbers and quiet attribution. Keep sensitive details out of public templates; prominently label fictional samples. Export selectable text, headings and real tables where possible, then inspect reading order and links.

Start with `template-slide-title.svg/png` and `template-slide-section.svg/png`, both 1920×1080; `template-report-cover.svg/png`, 1240×1754 with an A4 ratio; or `template-research-square.svg/png`, 1080×1080. Edit document text while preserving outlined logo artwork. An A4-ratio pixel export does not specify final print resolution, trim or bleed. Confirm those settings for the real document.

For slides, use one main idea and a quiet margin. Put sources beside claims and small attribution in a predictable position. Use a full lockup on the title slide and less branding inside. Editorial covers need a title, content type and date where useful, not a service catalog. The site share-card convention is 1200×630; LinkedIn URL-post guidance recommends 1200×627, so inspect a platform-specific crop when needed.

`email-signature.html` supplies an HTML example. Test it in the intended mail client with images blocked before adoption. Keep this compact plain-text fallback:

```text
Raiders | Founder, Web3Sec
Independent security. Clear decisions.
https://www.web3sec.news/
Telegram: https://t.me/Raiders0786
```

If Google displays an old title, first verify the deployed title, description, canonical and indexability. In an authorized Search Console property, inspect the exact URL, test the live page and use **Request indexing**. Record the action after submission. [Google controls recrawling and inclusion](https://developers.google.com/search/docs/crawling-indexing/ask-google-to-recrawl); repeated requests do not accelerate it or guarantee a particular title or ranking.

## 10. Merchandise and production

These directions describe applications, not manufactured inventory or a shop. `application-sticker-sheet.svg/png` and `application-tee-placement.svg/png` are placement studies, not validated die-cut paths, sewing patterns or production specifications. The generated `concept-field-kit` and `concept-workshop-desk` PNG/WebP images are visual explorations, not photographs of manufactured products. Start with an actual use, give the mark room and include personal contact information only when intentionally chosen.

Send an outlined production logo master, a placement proof, finished dimensions, material, print position and intended colors. Agree bleed, safe area, dieline, tolerances and any white underbase. Keep detail away from cuts, folds, seams and stretch zones. Transparent screen artwork does not specify white-ink production.

Embroidery, engraving and small screen prints may need single-color artwork. Test tile gaps and corners at the selected size. Choose physical spot-color swatches or thread samples with the producer; this guide supplies no Pantone equivalence or thread code. Mathematical CMYK conversions will not guarantee a monitor match.

Approve an actual-size proof on the intended substrate before quantity production. Inspect color under appropriate light, edges, tile separation and positioning. Agree relevant washing, abrasion or durability checks. Record supplier, artwork version and approved sample. Label a mockup as a mockup until a real product is produced and photographed.

## 11. Distribution and maintenance

Downloadable artwork supports accurate identification. It is not a trademark registration claim, formal brand license or permission to imply sponsorship. Ask Raiders before co-branding, modifying the mark, merchandise sales or endorsement-like uses. Third-party logos, quotations, photographs and font software retain their own requirements. Do not add a registered-trademark symbol without a verified basis.

Download bundles under `public/brand/` are `brand-kit.zip` (complete), `logos.zip` (logo artwork), `social-kit.zip` (profile and cover exports) and `templates.zip` (editable templates and application boards). Supporting files are `design-tokens.json`, `colors.css` and `palette.ase`; the ASE contains **RGB swatches**, not a press profile. `brand-manual.html` is the reading/print view. `brand-guide-v2.pdf` is an optional generated export: check its presence before linking it.

Keep production masters, editable sources, PNGs, manifest and dated guide together, with their roles clearly named. Inspect the contact sheet, dimensions, transparency, small-size legibility, crops and links before release. SVGs remain static with no scripts, remote assets or embedded secrets. Remove superseded files from external handoffs. Regenerate manuals and bundles after guidance changes so downloaded copies match the public page. Review the instructions when services, attribution, channels, artwork or platform specifications materially change.