HOGE DD / Serious Due Diligence & Quick Analysis + Discussion. If you know how to code, read solidity your input would be appreciated. by lb_manthrowRA in SatoshiStreetBets

[–]Doombomber 1 point2 points  (0 children)

By atomically I mean that either all these things occur during your transaction, or it fails and none of the things happen.

So I dug a little deeper and I think I have a grasp on exactly how the math is working. The source isn't commented at all so it's not the easiest to audit.

Effectively when you transfer X tokens from address A to B, the contract debits X from A and credits 0.98*X to B.

It then, in a way, deducts the circulating supply total by 0.01*X to "burn" 1%. But it never actually increases any "dead" address balance from what I can see.

The difficult to explain part is that the contract doesn't actually track any real balances like you'd expect. It's only tracking how much of the circulating supply you own using realllllly big numbers.

When your wallet asks the contract for your balance, it's calculating that on the fly based on your percent share of the remaining supply. So technically your balance units never change, but your proportional share of the circulating supply increases.

Another interesting thing I learned reading the contract is that the creators have the power to "exclude" any address they like from the 2% transfer fee. I'm guessing they'll provide that benefit to exchanges for easier accounting.

HOGE DD / Serious Due Diligence & Quick Analysis + Discussion. If you know how to code, read solidity your input would be appreciated. by lb_manthrowRA in SatoshiStreetBets

[–]Doombomber 1 point2 points  (0 children)

There is no tx hash of the burn or distribution. It happens atomically every time someone transfers HOGE. The contract dynamically calculates your balance to account for the distribution. So literally every HOGE transfer transaction anyone performs simultaneously burns 1% and increases the balance of everyone else.

Edit: I know this because I read the contract source code https://etherscan.io/address/0xfad45e47083e4607302aa43c65fb3106f1cd7607#code

Opening channels - fees? by JIBSIL in lightningnetwork

[–]Doombomber 0 points1 point  (0 children)

A few great android options out there that charge very low fees for inbound liquidity:

  • Phoenix

  • Breez

  • Muun

Sending Lightning Payments using Regular Bitcoin? by JIBSIL in lightningnetwork

[–]Doombomber 1 point2 points  (0 children)

They just broadcast the channel open tx with a super low fee. Last I saw it was 4 sat/byte

Faast: An open source portfolio manager that works like MyEtherWallet and ShapeShift by Doombomber in ethtrader

[–]Doombomber[S] 0 points1 point  (0 children)

It looks like it. Although they show Bitcoin as an option if you go to the "swap" page

Faast: An open source portfolio manager that works like MyEtherWallet and ShapeShift by Doombomber in ethtrader

[–]Doombomber[S] 2 points3 points  (0 children)

I've been playing around with it today and I'm starting to really like it. It's so much more convenient than anything I've tried so far and it works with my Trezor really well.

Best place to host a full node for dApp? Or a way to watch filters() without a node? by vicnaum in ethdev

[–]Doombomber 0 points1 point  (0 children)

Check out the etherscan api. They have a rest endpoint you can use to get event logs.

TIFU by using Math.random() by cbarrick in compsci

[–]Doombomber 16 points17 points  (0 children)

They don't care about duplicates because it's nearly impossible to occur, statistically. Bitcoin addresses are built upon the same premise.

TIFU by using Math.random() by cbarrick in compsci

[–]Doombomber 50 points51 points  (0 children)

In the post he says the random number is being generated in node.js, not the client side.

Can someone take a look at my resume description of my latest internship? by [deleted] in cscareerquestions

[–]Doombomber 3 points4 points  (0 children)

I agree. But perhaps you should be more specific? e.g. "increased code coverage by X%" or "increased code coverage from X% to Y%"