FF14 / FFXIV WoL
BLM Hrothgar ♥
hroths are a challenge to draw but it was a very fun one, incredibly satisfying!
FF14 / FFXIV WoL
BLM Hrothgar ♥
hroths are a challenge to draw but it was a very fun one, incredibly satisfying!
A3: Celebrating Velmere: an outdoor winter festival that honors the Printmaker who supposedly gave people their powers over ink, metal, and cloth.
Ness isn't religious. She enjoys the food, drinks, bonfires, and artistry on display.
Question Three:
What's your characters’ favorite seasonal activity?
Next question at :35!
@theodoresnapdragon.bsky.social #QueerWriters #writesky #writers
A3: Celebrating Velmere: an outdoor winter festival that honors the Printmaker who supposedly gave people their powers over ink, metal, and cloth.
Ness isn't religious. She enjoys the food, drinks, bonfires, and artistry on display.
Public SmartBugs checkpoint:
22/22 detected in the supported + executable subset.
7 withheld, never marked safe.
OpenZeppelin controls: 2/29 alerts.
No “100% security” claim. Next: full corpus + audited-code replay.
Public SmartBugs checkpoint:
22/22 detected in the supported + executable subset.
7 withheld, never marked safe.
OpenZeppelin controls: 2/29 alerts.
No “100% security” claim. Next: full corpus + audited-code replay.
Harder stress tests exposed gaps in false-positive control, mutation stability and reentrancy/call-graph detection.
That’s now the focus.
#Web3Security #SmartContracts #Velmere
Harder stress tests exposed gaps in false-positive control, mutation stability and reentrancy/call-graph detection.
That’s now the focus.
#Web3Security #SmartContracts #Velmere
We're benchmarking Velmère against CertiK, OpenZeppelin and other top security firms and we're publishing our own failures too.
Our goal: better security, faster audits, radically lower prices.
Velmère is coming.
We're benchmarking Velmère against CertiK, OpenZeppelin and other top security firms and we're publishing our own failures too.
Our goal: better security, faster audits, radically lower prices.
Velmère is coming.
For Velmère, I’m working toward a clearer missing-data experience: what’s missing, which conclusion it limits, and what evidence to check next.
What’s the most useful explanation you’ve seen in an incomplete report?
#DataQuality
For Velmère, I’m working toward a clearer missing-data experience: what’s missing, which conclusion it limits, and what evidence to check next.
What’s the most useful explanation you’ve seen in an incomplete report?
#DataQuality
Less “build more features”, more testing what actually helps real teams.
Security, RWA evidence, market data, identity/KYC and provider integrations are the conversations we want next.
No hype. Just useful work.
Less “build more features”, more testing what actually helps real teams.
Security, RWA evidence, market data, identity/KYC and provider integrations are the conversations we want next.
No hype. Just useful work.
Keep testing privately with dozens of audits + different AI customer personas?
Or open an imperfect beta earlier and improve it with real users?
I’m leaning toward a mix of both, but curious what you’d prefer.
Keep testing privately with dozens of audits + different AI customer personas?
Or open an imperfect beta earlier and improve it with real users?
I’m leaning toward a mix of both, but curious what you’d prefer.
Velmère is testing a narrow typed allowlist, not a weaker privacy filter.
Anyone else been bitten by “safe” regexes deleting valid evidence?
Velmère is testing a narrow typed allowlist, not a weaker privacy filter.
Anyone else been bitten by “safe” regexes deleting valid evidence?
Model Base: Kikyo
Outfit: Velmere
Hair: PoyTail
Ears/Tail: Star Set
Tattoos: Spring Season Pack
Eyes: Glass Beads
Skin/Scar Textures: Me!
Hair Clips: Animal Hair Pins & Nemukuma Hairpin
Model Base: Kikyo
Outfit: Velmere
Hair: PoyTail
Ears/Tail: Star Set
Tattoos: Spring Season Pack
Eyes: Glass Beads
Skin/Scar Textures: Me!
Hair Clips: Animal Hair Pins & Nemukuma Hairpin
Today Velmère reconstructed a 1,597-file build projection twice, byte-identical, with 0 mismatches.
I still won’t count it as a Windows pass until the native run exists. Too strict, or the right boundary?
Today Velmère reconstructed a 1,597-file build projection twice, byte-identical, with 0 mismatches.
I still won’t count it as a Windows pass until the native run exists. Too strict, or the right boundary?
I’m testing a CONFLICTED state in Velmère instead of quietly picking one number. If the disagreement matters, deeper analysis can be limited until the evidence is resolved.
Stop, reduce scope, or show both and continue?
I’m testing a CONFLICTED state in Velmère instead of quietly picking one number. If the disagreement matters, deeper analysis can be limited until the evidence is resolved.
Stop, reduce scope, or show both and continue?
“unknown” should be a first-class result, not an error state.
Stale data? Sources disagree? Unsupported contract path?
Show it.
A security tool earns trust partly by knowing when it shouldn’t guess.
“unknown” should be a first-class result, not an error state.
Stale data? Sources disagree? Unsupported contract path?
Show it.
A security tool earns trust partly by knowing when it shouldn’t guess.
Missing evidence, conflicting sources and “unknown” states shouldn’t be hidden just to make a dashboard look cleaner.
I’d rather earn trust slowly than manufacture certainty.
Missing evidence, conflicting sources and “unknown” states shouldn’t be hidden just to make a dashboard look cleaner.
I’d rather earn trust slowly than manufacture certainty.
“unknown” should be a first-class result, not an error state.
Stale data? Sources disagree? Unsupported contract path?
Show it.
A security tool earns trust partly by knowing when it shouldn’t guess.
“unknown” should be a first-class result, not an error state.
Stale data? Sources disagree? Unsupported contract path?
Show it.
A security tool earns trust partly by knowing when it shouldn’t guess.
If Velmère flags something, I want it to show what triggered the warning, what evidence exists and what’s still uncertain.
What makes you trust a security/risk score?
#Web3Security
If Velmère flags something, I want it to show what triggered the warning, what evidence exists and what’s still uncertain.
What makes you trust a security/risk score?
#Web3Security
We’re working on security audits, crypto risk tools, real market data and cleaner research reports — all in one place.
Still testing, but we’re getting close. 👀
We’re working on security audits, crypto risk tools, real market data and cleaner research reports — all in one place.
Still testing, but we’re getting close. 👀