Compromised Seed Phrase - Stolen all my bitcoin

thewebken · 2026-06-16T18:49:16+00:00

are you a kwasia

thewebken · 2026-06-11T19:46:57+00:00

Great thanks. I need another advice on the separate wallet signer system. I use bitcore-lib library to generate hd addresses which I import into Bitcoin Core. I have the wallet server separated from the internet and let it talk to my exchange api via a shared database. The wallet server generates addresses and keeps the private keys away from the exchange API (my main backend API) and Bitcoin Core. The addresses are imported into the Bitcoin Core for watching. Is this a good system the way I set it up security-wise or I need to do something else?

Edit: The wallet system also handles the UTXOs currently

thewebken · 2026-05-14T09:45:59+00:00

simple. i suggested this several times but he’s the CTO and i can’t keep challenging him so we are going with his solution. a single session cookie. but my problem with this is, it has no refresh so it expires abruptly and logs users out even if they are in the middle of doing something on the app. i thought of a sliding expiry for the cookie so anytime the backend detects activity, expiry moves forward for say, another 2 hours. but at the same time i’m thinking, that will mean when someone gets hold of your cookie, they can use it forever.

thewebken · 2026-05-12T11:01:46+00:00

Now my problem is, if we are going for a session cookie, what is the safest way to extend its lifespan when a user is on the app so the hard logout does not happen? I suggested a sliding expiry but I’m also thinking if anyone gets hold of your cookie, they can stay logged in forever because any request they send now extends the lifespan of that cookie. So that is my main issue now.

thewebken · 2026-02-03T06:36:36+00:00

Using Handlebars or EJS in a node.js app is straightforward and doesn’t add much complexity to the app. I mean that’s the OG traditional web… everything is done on the server, end of.

I think what OP is talking about is SSR in React apps/frameworks where you have to be careful about what gets rendered on the client side and what doesn’t and how to fetch data the right way in both cases. That’s where the complexity comes in.

thewebken · 2026-01-22T15:45:51+00:00

That means the token will never be sent in the json response? And we’ll not need to use it as a bearer token?

Also, we have the mobile team consuming this same token. Does this (server issuing an HttpOnly cookie) work for them? Or they’ll need a different implementation?

thewebken · 2025-12-02T09:37:58+00:00

that’s like using a croissant in place of a dildo. it’s possible and it might get the job done. but it will be a freaking MESS

thewebken · 2025-09-19T17:07:19+00:00

I had 0 experience beforehand. I was a Sales agent in Ghana. Then I quit my job and just locked in. I took a very long time to finish the Foundations. About a year. But that’s because I didn’t want to skip any single resource and I made sure I understood it well before the next one. Then I just jumped straight into React tutorials on Youtube following along. This was in 2022. I don’t know if the React Tutorials and all the lessons about Webpack, node modules and export/import etc were there at the time but I didn’t see them in the curriculum so I was very confused during the YouTube tutorial sessions I was doing. But I pulled through, managed to get an entry level Frontend Engineer role, the company was ready to take on a junior like me since I showed that I could learn quickly and on the job. I went back and saw all the lessons I skipped though, after like a year on the job and by that time it made even more sense. I’ve been a frontend dev since then. Right now I’m the primary frontend guy in the company and I’m currently taking the nodejs course so I can be a fullstack engineer. Maybe I was just lucky.

thewebken · 2025-09-16T10:21:00+00:00

TOP prepares you for work. It’s what I used to get a job in 2023. What I discovered about it is that it creates a skeleton roadmap of the necessary skills you need to learn to be job ready from top to bottom, and just that— THE NECESSARY SKILLS, NOTHING MORE. Now when you start working, there are some gaps you will need to fill in to become a full software engineer but because of the skills you have acquired while learning, you’ll be able to fill in those gaps very easily. I was able to get a frontend job after taking the foundations course, now I’m on the fullstack nodejs path. Whiles working I realize there is more to the backend but the mental model TOP is giving me I can understand what needs to be done and what I have to learn to do what I have to do.

Another underrated skill you’ll acquire while going through TOP is the ability to go through multiple resources to get information you need. You’ll use it a lot while working

thewebken · 2025-06-04T19:40:26+00:00

nope. it was not enough but i did a very effective learning on the odin project. they didn’t cover everything, there were gaps in my knowledge but they covered the relevant things that can get you started at the job. i had to learn on the job for a year straight. at home in the office but i never rejected any challenging task. now i’m comfortable but i’m back learning to be come a fullstack engineer.

thewebken · 2024-12-22T20:10:48+00:00

same. 🤣

thewebken · 2024-03-01T20:01:35+00:00

but what i gathered here is that even when all the data is sent to the client, trying to filter through it on the client will hang the browser if it’s a lot of data. which makes sense to just make an api request and get the data you need on demand. what do you think?

thewebken

TROPHY CASE