1. All you need to do are import the private key from your paper wallet to your Bitcoin wallet. 2. It's possible to send Bitcoin to multiple address in a transaction. 3. While you can send remaining Bitcoin to same address on your paper wallet, it's strongly not recommended to do it due to privacy and security concern.
|
|
|
Since i know the fact all software related to LN is still on development phase & i had hard time when try LN on testnet, i won't. I might try it if someone can confirm the software support Tor/SOCKS5 proxy though. either 1MB (you're wrong, it's 4MB)
Technically it's 4 million weight unit, not 4MB (even though near 4MB with very specific transaction format) or 1MB (even though old client see it as 1MB)
|
|
|
From where I'm at, I can snatch a WD Black for at least $60, and that's already a 1TB drive, brand new. If the user wouldn't be picky enough and know how to clean a drive properly, one can get a 1TB Black drive for about $40-$50, with 90-99% health.
It's a bit more expensive in here & price difference between regular 7200 RPM HDD and WD Black is quite wide while there's no significant performance difference on daily usage. and I don't think they are selling 320GB drives brand new anymore--or I haven't stumbled upon anything within the past few years of changing systems.
So does 250GB HDD which you mentioned earlier. But if you're lucky, you could get one which never used because no one buy it Anyway, if someone isn't that picky a Blue/Black drive secondhand would suffice and just transfer the chainstate on the OS drive which, in this case is a SSD.
I agree, but i wouldn't risk buy second-hand/used drive, even if it's properly tested before it's sold.
|
|
|
IPFS is only a solution for a decentralized file hosting. The rest is just the usual coding stuff. If people create accounts, they can apply permissions to anyone they want. A little bit like OpenBazaar > 2.0, only that these accounts could be shared with other participants based on the permissions, that the account owner provides. Shouldn't be a big issue or did I miss something here?
Edit: Account holder can also be a group that shares a multi sig key.
Good idea, i didn't think combining IPFS with another system such as OpenBazaar account. All developers & contributor needs to understand the value of their keys though. I think GitHub is trying to comply on where you live, which makes it more legitimate and trustworthy.
Perhaps, but most people who affected are innocent (not involved or directly support whatever which cause U.S. make this law)
|
|
|
LN will never be solution, Satoshi said that onchain transactions will support miners in the future, with LN there is no fees for the real miners that support blockchain, with time the fee of one ON-CHAIN transaction will be huge.
Only fools who say LN will solve all scaling problem, besides LN still need on-chain transaction to open & close channel. IMO LN only useful for those who often make micro-transaction. LN will have low fees but On-Chain will have a impossible fee to pay and who will rule the LN chanels will be the same as banks, we are not in control of our money!
LN basically bunch of un-broadcasted transaction with timelock, we have control over our money. The real problem is when other party is unresponsive or non-cooperative where we're forced until timelock expired. We need to think about a scalling solution that splits the blocks in blockchain groups, like group A, B, C and so on, that number of groups will be bigger with the number of nodes running, that way the size of block will be always 1MB by node, node type A, node type B and so on, they could be splitted in many 1 MB parts of a block an tested online like SPV wallets.
It's called Sharding & already exist for years. The hard part is convincing the community to use sharding. If bitcoin was used by all the people of the world they will not to be all nodes, so, we can have one node for some % of people, the same way we dont need to have 100% full node information by each node, so, we can split like prunned nodes, some have some blocks, some have other blocks, that way we can scale blocksize and if we scale blocksize we can have some pruned nodes registering 1st 1 MB of the block and other nodes registering 2nd 1MB and others registering 3rd 1MB of the blocks, why not?
Irrelevant, regular people don't bother run full nodes, they will always rely on SPV or custodial wallet. If we make this auto-scalling by the number of existing nodes and transactions we can do it without Lightning Network bullshit that its even worst as banks!
To verify total of full nodes, a node must connect to all full nodes where : 1. Most device can't connect to thousand nodes at once 2. De-anonymization because all nodes who broadcast a transaction/block 3. Full nodes have low default incoming connection limit (AFAIK it's 125) To solve the huge number o information in all network there is another solution, we start to delete 1st blocks of blockchain after some number of blocks, example GENESIS block can be deleted and the money still in that address can be reward for miners, this is the best solution for any database, all databases in the world cant grow up infinitely, that is fisically impossible and will waste a lot of resources, so we need to start do delete blocks sooner or later, why dont do the perfect machine now and dont let problems for future generations solve like Y2K in year 2000 ?
Pruned mode already realize your idea, user just need to store set of UTXO, recent blocks & all blocks header (which is only 80 bytes/block).
|
|
|
There aren't noteworthy changes since 2017 for regular user, but there are few upcoming changes such as : 1. Schnorr Signature, which reduce transaction size when there's more than 1 input 2. Taproot, which reduce P2SH/script size & uses Schnorr 3. Few soft-fork (about scripting mostly) to make other update can be implemented into Bitcoin
There's no ETA when those changes released though
|
|
|
Usually uninstall and reinstall both BTC and ETH would solve the problem. On my experience, it might happen if the application for BTC and ETH are outdated.
Make sure uninstall other application which require BTC or ETH before remove BTC or ETH though.
|
|
|
Sorry for Bumping this. & thanks for creating it. I've made some edits to update the page after sending sMerits. Is it possible to display full sMerit amount on the same screen? sMerit and source Merits. Something like this
Edit: Not only @ EcuaMobi update but total amount (Merit source + sMerit) It's piece of cake, i've made slight modification for your need : // ==UserScript== // @name bitcointalk merit // @namespace grue // @include https://bitcointalk.org/index.php?topic=* // @require https://ajax.aspnetcdn.com/ajax/jQuery/jquery-3.3.1.min.js // @version 1.1.1 // @downloadURL https://grue.blob.core.windows.net/scripts/Merit.user.js?sv=2014-02-14&si=1&sr=c&sig=k%2BqstGBI3oQ8TrHfPWjS5HgjrazuDPmKJ6rYNs7rvRk%3D&.user.js // @grant none // ==/UserScript==
(() => { var sMerit; var source_sMerit;
//get csrf token from the logout link let sc = $('td.maintab_back a[href*="index.php?action=logout;sesc="').attr("href"); sc = /;sesc=(.*)/.exec(sc)[1];
//Added by EcuaMobi: Get remaining sMerit $.post( "https://bitcointalk.org/index.php?action=merit;msg=29048068" ).then((data) => { sMerit = /You have <b>([0-9]+)<\/b> sendable/.exec(data)[1]; source_sMerit = /The next ([0-9]+) merit you spend will come from your source/.exec(data)[1]; }).catch(() => sMerit = null);
//selector for the "+Merit" link $('td.td_headerandpost div[id^=ignmsgbttns] a[href*="index.php?action=merit;msg="]') .each((i, e) => { const msgId = /msg=([0-9]+)/.exec(e.href)[1];
const $popup = $(['<div id="grue-merit-popup' + msgId +'" class="grue-merit-popup" style="position: absolute; right: 40px; background-color: #ddd; font-size: 13px; padding: 8px;border-width: 1px;border-color: black;border-style: solid;">', ' <form>', ' <div>', ' Merit points: <input size="6" name="merits" value="1" type="text"/>', ' </div>', // Modified by EcuaMobi ' <div style="margin-top: 6px; "><span id="em-smerit-count' + msgId +'" style="font-size:11px;" /> <input value="Send" type="submit"></div>', ' </form>', '</div>' ].join("\n")); $popup.find("form").submit( (e) => { e.preventDefault(); $popup.find('input[type="submit"]') .prop("disabled", true) .val("Sending..."); const merits = e.target.elements["merits"].value;
$.post( "https://bitcointalk.org/index.php?action=merit", {merits, msgID: msgId, sc} ).then((data) => { //Error pages usually have this (rough heuristic) if(data.includes("<title>An Error Has Occurred!</title")) { throw "error"; } //double check and see whether the post we merited was added to the list. Its msgId should be visible in the page source. if(data.includes("#msg" + msgId)) { alert("Merit added."); $("#grue-merit-popup" + msgId).toggle(false); // Added by EcuaMobi if(sMerit!=null) { sMerit -= merits } return; } alert("Server response indeterminate."); }) .catch(() => alert("Failed to add merit.")) .always(() => { $popup.find('input[type="submit"]') .prop("disabled", false) .val("Send"); }); }); $popup.insertAfter(e);
$(e).click((e) => { e.preventDefault(); $("#grue-merit-popup" + msgId).toggle(); // Added by EcuaMobi if(sMerit!=null && source_sMerit==null) { $("#em-smerit-count" + msgId).html('<a href="https://bitcointalk.org/index.php?action=merit;msg='+msgId+'" target="_blank">Available:</a> <b>'+sMerit+'</b> ') } else if (sMerit!=null && source_sMerit!=null) { $("#em-smerit-count" + msgId).html('<a href="https://bitcointalk.org/index.php?action=merit;msg='+msgId+'" target="_blank">Available (yours | source):</a> <b>'+sMerit+' | '+source_sMerit+'</b> ') }; }); }); $(".grue-merit-popup").toggle(false); })();
It's based on version 1.1 & i separate personal and source merit amount. I did it in a minute, so i hope there aren't any logic error. Edit : screenshot if you're merit source. If you're not, it's exactly same with version 1.1
|
|
|
That depends on the blockchain protocol & consensus. If other miner & node decide to ignore block created due to 51% attack, re-org process will happen instantly, but will cause hard-fork. If it's ignored, blocks generated due to 51% attack will stay on longest chain.
Take note chain rollback/re-org doesn't always happen because 51% attack. It might happen when there's orphan block ,where 2 different miner create a block almost at same time and one of them isn't on longest chain.
|
|
|
You can use a bash script to import multiple keys, first of all put all those keys on a text file and then you can run something like: for a in $(cat keys.txt) do bitcoin-cli importprivkey $a done By default, Bitcoin Core will rescan whole blockchain to find all transaction related to the imported private key. If OP insist use Bitcoin Core, i think skip scanning when import private key & perform scan after all private keys are imported is more efficient. for a in $(cat keys.txt) do bitcoin-cli importprivkey $a "" false done
bitcoin-cli rescanblockchain
|
|
|
How about use another Bitcoin full node client which claim offer better performance in this case, such as https://bitcore.io/? Take note client besides Bitcoin Core might be outdated & not thoughtfully tested unlike Bitcoin Core. You can hide a lot of programming things with better hardware. NOT an ideal solution but it can help you with your coding.
Many desktop/mobile application usually uses same practice, sacrifice performance/complexity for faster development to continuously satisfy customer with new features. But it's horrible practice in this case since the application won't scale with complex hardware (multi-core CPU, multiple CPU, big RAM & multiple server). Just my thoughts. I am not a programmer I'm the hardware guy. But I have seen some things that were SOOOOOO badly written that 5 x the hardware did not make a difference in the application speed.
It's also the possible there's bottleneck with other hardware (such as CPU, GPU or RAM), bottleneck with slow internet connection or the task performs is either CPU, GPU or RAM intensive tasks.
|
|
|
What is the estimated percentage of bitcoin nodes that are full nodes (keeping the whole history) and what percentage are SPV nodes (which keep only the block hashes)?
I don't remember any website or service which have such detailed information. Besides statistic of full nodes which accept incoming connection, Luke Dashjr write a software which shows total Bitcoin nodes at https://luke.dashjr.org/programs/bitcoin/files/charts/software.htmlbut it doesn't seem to tell us whether these nodes are full nodes, archival nodes, pruned nodes, light nodes, spv nodes
Those terms usually when we're talking about Ethereum. From what i've seen, most people only talk about full node & pruned full node. SPV and light node usually not acknowledged as node. Is there a way to somehow distinguish them?
By looking services offered by the nodes, such as NONE, NETWORK, GETUTXO, BLOOM, WITNESS & NETWORK_LIMITED. See https://github.com/bitcoin/bitcoin/blob/master/src/protocol.h#L247 for more info. https://bitnodes.earn.com/nodes/ shows services of each known full nodes. But you still need to obtain & process those information manually to build statistic you need, fortunately they provide an API
|
|
|
--snip--
So yeah, that's another ~20 years without crossing 21 million BTC and I'm sure if I kept going, it's okay for some time, or possibly forever.
Actually, it will never cross 21 million BTC as long as the only thing changed is halving every 210.000 blocks happen forever rather than until the mining reward is 1 satoshi. It's just like math problem/logic where if you sum 1/2, 1/4, 1/8, 1/16, ..., 1/2 n is less than 1
|
|
|
15 maxconnections means you allow 8 outgoing & 7 incoming connection which won't help you sync faster. AFAIK you can't increase maximum outgoing connection without modify source code of Bitcoin Core. If Bitcoin Core doesn't use maximum speed of your connection and CPU/Storage isn't holding back (bottleneck), you might want try your luck by connect to different node (usually closer to your region). See https://bitnodes.earn.com/ for list of known nodes which accept incoming connection.
|
|
|
|