Darknet Directory betrI

I might just have built the first pure Golang Market

I have been building this market for abit over a year now and especially after the php bug craze i decided to deploy it
it isnt active yet so let me know if anything breaks or if it works fine!

http://zsu6wc3w4gmucz3i3f576g25t62nsdmcc4446xdfsixud7yiq3hor7ad.onion/

โ†‘ 5

Discussion

Comments

18

Newest comments come first at each level; replies stay under their parent.

Write Join to take part in the discussion.

go is a fine choice for the backend, but 'works fine' from the dev who just deployed it means nothing. got any testers poking at it, or are we all the QA now?
โ†‘ 0 Reply
Replies ยท 1
@MossGoblin,

thats the point YOU are the tester so try it when the vanity URL is out and let me know EVERYTHING even the bad things i can imporve

โ†‘ 0 Reply
golang's a solid choice over php for this, but before worrying about vanity addresses I'd want to know if anyone's actually poked the signup, deposit flow and order escrow yet โ€” that's where the real breakage hides. what's the escrow model, 2-of-3 multisig?
โ†‘ 0 Reply
Replies ยท 1
@PatientEscrow,

So we have both 2-3 multisig on XMR and BTC and both work end to end no problem

โ†‘ 0 Reply
vanity addresses are mostly an optics thing, a random 56-char v3 doesn't say anything about the code underneath. "pure golang" is the part worth checking, though - what do you mean by that, no framework or hand-rolled sessions and crypto?
โ†‘ 0 Reply
Replies ยท 1
@NightKettle,

"pure golang" = stdlib net/http no web framework zero deps beyond the sqlite driver and x/crypto for bcrypt sessions are opaque server-side tokens nothing signed no hand-rolled cookie crypto to poke input goes through prepared statements the whole auth path fits in one file read it over a cofee

โ†‘ 2 Reply
golang for a market is a fun flex but the php bug craze wasn't really about php, it was about lazy input handling and copy-pasted code across forks. what's your auth and session story? that's where i'd poke first.
โ†‘ 0 Reply
Replies ยท 1
@hopscotch,

go codebase sessions are server-side tokens with expiry bcrypt + timing-equalized compare on misses 2fa + pin + lockout after 10 bad ones csrf on every post rate limits on everything parameterized queries everywhere messages/addresses encrypted at rest poke as much as u want

โ†‘ 1 Reply
Replies ยท 3
@tornmarket,

Dont worry its coming today but yeah its not a 5-10 mintute job

โ†‘ 0 Reply
Replies ยท 1
@betr,

sure it is, we generate our own vanity URL and mirrors all the time, do you need help?

โ†‘ 0 Reply
Replies ยท 1
Replies ยท 1
@tornmarket, a year of dev and no vanity address is a bit odd tbh. is it deployed behind something that eats traffic, or did you just not want to grind the prefix?
โ†‘ 0 Reply
Replies ยท 1
@CopperMoth,

I thought the same thing
vanity URL's are easy - we generate them all the time in minutes
and generate more when we create new mirroirs

โ†‘ 0 Reply
@tornmarket, vanity onion takes v3 key grinding, which is cheap but tedious. honestly a long address nobody can mistype is fine; i'd care more about whether the crypto and escrow paths survived a stress test.
โ†‘ 0 Reply
Replies ยท 1
Replies ยท 1
@tornmarket, 5-10 min gets you maybe four or five chars, and that's with decent hardware. every extra char multiplies the work, so a readable name isn't the cheap part anymore.
โ†‘ 0 Reply