[snowblossomcoin/snowart] #1 Add files via upload

[snowblossomcoin/snowart] #1 Add files via upload

[snowblossomcoin/snowart] #2 updated vector logos

@Fireduck things are moving faster than i have had time to actually read the code - how's the deal with broadcasting transactions, i suppose the client does the signing? some overview level flow charts would do well

@Fireduck i'm seeing people heading in a way where they offer open nodes, and i'm not on top of what's the power of the node - they can at least silently gobble up and not broadcast your transactions and just tell you false data, but no idea of what exactly does what - i'm assuming it to be somewhat sensible, though

@Rotonen Clients handle wallet data and signing, yes, and broadcast through a node. -- Without having gone over the technical details, my understanding is the node maintains a `UTXO graph`, which represents the `UTXO set` *If implemented*, a client can be given the `UTXO hash` and `UTXO tree path` to an address to *prove* that address truly has those balances. However, if not, it could lie, as the client would be trusting the node.

*https://github.com/snowblossomcoin/snowart/compare/6be253aa786d...59094464b080* https://github.com/snowblossomcoin/snowart/commit/5c9a578aaa3f86386551a454f14fd87cb6dac0e9 - Create snowblossom_logos https://github.com/snowblossomcoin/snowart/commit/03093c34bbe95dbb162cbbf01839028c955dd52d - Delete snowblossom_logos https://github.com/snowblossomcoin/snowart/commit/72c83b1f9f3ae6d2df2a37ce8b6b754ee5f83543 - Create updated logos https://github.com/snowblossomcoin/snowart/commit/ca042d10f072bebf9fe606912b397b3657d179a5 - Add files via upload https://github.com/snowblossomcoin/snowart/commit/59094464b080a1562a069c4bc9a73d8b16c55458 - Merge pull request #2 from vectorshape/master

[snowblossomcoin/snowart] #2 updated vector logos

@Rotonen ``` version: 1 block_height: 26024 prev_block_hash: "\000\000\000\000\000\251\005Oyg\3306\202\266\352\356\346n\322\362\204\263O4\214Iy\n\276\326d>" merkle_root_hash: "0\r^z6B\303\237\253\263\335O\360\324P\243<\002k\325\032!\000\214\026\327uq\252\267sy" utxo_root_hash: "\305\017WBzY\363\207\037\252\020\364\2203\037U\316\362\226\237\314\031(\371\245x\324\350\031t\256," nonce: "\327wS\223\010\346\003[\246u\340E" timestamp: 1541339971341 target: "\000\000\000\000\000\323\310S\336x\304\332\200m\0036\354)\233L\206\000(:n\336\200\343VFjv" snow_field: 7 snow_hash: "\000\000\000\000\000b.#\345\000L\332\205\376\252\262\322SB\305*</\025T\333\240\026\346hx\250" ``` These are the fields (minus the POW proofs) in the block headers `utxo_root_hash`

is that helpful?

Nodes can't hide information from the clients, unless they lie about which block is the head

eventually, I'll make that rather hard as well

but for now, the clients validate what they are giving against the utxo header

Sweet, I didn't realize that was implemented yet.

yeah, GetUTXOUtil

used by client and explorer

*https://github.com/snowblossomcoin/snowblossom-python/compare/df51e3d4195c...d9823a8be376* https://github.com/snowblossomcoin/snowblossom-python/commit/d9823a8be37679d22739a5203b1d33d986e332b9 - add ChainOrganizer, allows maintaining a chain including reorgs

A stat I want is key type

I wonder if anyone other than me is using qhard

*https://github.com/snowblossomcoin/snowblossom-python/compare/d9823a8be376...b2d080c0ec0d* https://github.com/snowblossomcoin/snowblossom-python/commit/b2d080c0ec0db42780fa25f015c1566550d91f3d - .

meh, bitcoin richmists will get bitten way earlier

@Rotonen what's a richmist?

Vaporized sapphire

... you made me google that you troll

Ha

Pow(2,diff) / 600

*richlist

@Fireduck oddly enough i've worked a lot in vaporized sapphire, i'll bump my inherent suspicion of you up a notch :stuck_out_tongue:

Ha, good

titanium and aluminium sputtering specifically

as @Clueless seems to be hungry for googlables