4,700 karma · joined September 29, 2011
I have a Chrome extension which is perfect for race attacks. https://github.com/sakurity/racer
I did many things wrong but still pretty happy with the results. Not a recommendation: I did zero marketing.
Monthly some cool bugs I did writeups about, which brought new clients, which brought new ideas, which I wrote up about again.
I quickly realized that (cringe) "rock star" name allows you to bill $500/hr, which I did. No one ever said "that's too expensive for us".
I think what tptacek and McKenzie are always saying is best advice indeed : increase your rates. Believe that you are worth that much, don't feel like an imposter.
The reports I've delivered contained great bugs but were poorly presented (no design, basic formatting). It could be done much nicer, so invest in your "receivable items".
Btc’s current limits are far from optimal but layer2 itself is working great especially on other chains.
Big blockers are new flat earthers.
The difference is synthetic balance is offered to be enforced from the collateral from the escrow. In XLN I proposed to try to enforce it by taking it from the other party's onchain balance.
Both options would work together even better ("synergy" haha)! From the first example:
1. blockchain dispute resolution code tries to take USDC from Alice's onchain balance (since Alice owes 750 to Bob).
2. if Alice still owes something, try to convert any other Alice's onchain balance into USDC using oracles, then return to Bob.
PS. will finish reading the paper sometime soon, so not sure if got it wrong.
Overall, happy to see new solutions coming to payment channels that do not imply full collateralization (via cross-asset synthetic collateralization as in here). Full prepaid collateral is stupid and limiting the growth.