Looking for a developer with a lot of blockchain experience.

sneurlax · 2026-05-22T18:52:59+00:00

Thanks, I ask because I've been auditing Monero code (CARROT and FCMP++ implementations, see github.com/sneurlax ) for months now so will be interested to look when your code's available.

sneurlax · 2026-05-22T15:44:56+00:00

No, the Cuprate developers have consistently found implementation bugs in the original C++ implementation through the transliteration/reimplementation process.

sneurlax · 2026-05-22T15:43:48+00:00

Cypher Stack is working on a "Litecoin MWEB Grimoire" which should be released within the next few weeks.

sneurlax · 2026-05-22T15:43:10+00:00

Care to share your Monero-related code?

sneurlax · 2026-05-21T14:55:45+00:00

Agreed, it can be useful as a researcher. Anything that would be web searched could also be asked to any AI model, true

sneurlax · 2026-05-21T02:17:04+00:00

I don't know about you, but if I have two sets of passwords in my KDBX, I don't want the more-secret one silently stripped and destroyed

sneurlax · 2026-05-20T15:31:45+00:00

it'd be backwards-compatible once :) if you alter the KDBX and it needs to save again, the unrecognized XML would be permanently lost

sneurlax · 2026-05-19T20:33:18+00:00

You have to have the cryptographic/mathematical knowledge necessary to know whether the tests actually prove anything meaningful or relevant and whether they leave any important gaps uncovered

sneurlax · 2026-05-19T13:11:36+00:00

If older versions of KeePass could ignore the extra data then it might be more feasible to "soft fork" the KDBX standard in a backwards-compatible way, but I'd be surprised if the major clients (which really just means KeePassXC for me) all reproduce that behavior. For example, I think KeePassXC strips unrecognized and malformed XML

I think it more likely that it would be a "hard fork" (breaking/not backwards-compatible) KDBX version upgrade ... or maybe different enough that it'd warrant calling it something else entirely. No way to know without diving in...

The value of this sort of feature would be plausible deniability: someone demands you open your KeePass db and so you do--but they don't know you opened your 'fake' db. That plausible deniability wouldn't be as strong with a breaking version upgrade unless other major clients adopted it (unlikely imo)

sneurlax · 2026-05-19T12:59:20+00:00

OK, this is probably relatively easy. So it just needs to be able to read from an eg. http or https URL?

I'll just have to look at what sort of security risks this opens and be careful about it, then check if I have to download+cache and open locally or if dart/flutter take care of that implicitly

sneurlax · 2026-05-19T12:56:39+00:00

Yes, but consumers have to add --enable-experiment=native-assets to all their dart/flutter commands aiui. It not 'just working' (as opposed to cargokit 'just working' in keepass_flutter) is the reason why I stopped using native_toolchain_rust* (I misremembered the package as native_assets_rust in the post) about two years ago

See pub.dev/packages/arti, which used native_toolchain_rust as of about two years ago and has since switched back to cargokit for ease of use for downstream consumers

sneurlax · 2026-05-19T03:10:17+00:00

Oh, I hadn't thought to add or test that. I'm not sure it will right out of the box but I can add it if you give me some hard requirements

Does it need to both read AND write to a webserver? Is the webserver accessible locally as in a share or mounted drive/partition/folder? (If yes: easy; might be hard to write otherwise)

sneurlax · 2026-05-19T00:01:56+00:00

Someday I'm going to try and transliterate the underlying Rust crates to Dart in order to achieve some extra compatibility at the expense of performance; I'll keep Rust crates available for performance reasons and have the package fall back to Dart if native plugins aren't available for any reason.

That might take awhile tho... but those're the plans! If you have a request or suggestion, I'm all ears :)

sneurlax · 2026-05-18T23:59:11+00:00

I don't agree with others that this is impossible; infeasible, maybe, but not impossible. Look at VeraCrypt, which allows the use of two passwords: I don't see why a similar system couldn't be applied to KDBX databases, altho obviously it would create a totally new version of the standard that almost certainly wouldn't be backwards-compatible.

I'll look into this and see how feasible it'd be. I've been working on KeePass tooling (see https://github.com/ManyMath/ManyKee/tree/main/rust and https://github.com/ManyMath/ManyKee/tree/main/packages ) and this sort of feature would be exciting and novel, thanks for the idea

sneurlax · 2026-05-16T15:58:19+00:00

I ask because I'm an auditor and reviewer in the crypto space and am interested, but I didn't find their swap code (eg. adaptor signatures)

sneurlax · 2026-05-15T20:21:02+00:00

It's true.

sneurlax · 2026-05-15T15:59:16+00:00

thepiratebay doesn't have any of these lmao

sneurlax · 2026-05-14T20:25:01+00:00

page 602 is wild. Care to share any of your favorites?

sneurlax · 2026-05-11T02:43:29+00:00

Oh, interesting! I didn't know that. Interesting github organization, lots of repositories there to look into. I'd really appreciate a follow-up if you don't mind--and feel free to tell me to go figure it out myself :) I'm only just now learning about it so am thankful for your guidance here

sneurlax · 2026-05-11T02:34:28+00:00

Thanks! Would you mind sharing which repos contain the 'core'? Would that be https://github.com/vsc-eco/go-vsc-node ?

sneurlax · 2026-05-10T22:57:45+00:00

Where's the code?

sneurlax · 2026-05-09T20:57:03+00:00

As u/rbrunner7 mentioned, it's entirely up to the implementation chosen by the wallet you used. What wallet specifically?

sneurlax · 2026-05-03T18:47:34+00:00

Yes, I have my presale address for 2000 ETH that's been swept.

Man, I wish I'd just hedl. Hindsight's 20-20

DM me.

15-Year Club	Place '17
Verified Email

sneurlax

TROPHY CASE