I can't follow this statement either..




This would work.
But if this web platform is only running on your server (without being open source), then what is the reason to use a blockchain?
You would create a centralised platform utilizing an inefficient data structure.

If you want to build a centralised platform, use another form of storage. A simple databse would be way more efficient.
If you want to build a decentralised platform, other people need the ability to connect to your network (without relying on your server/web application).

Theoretically, yes. This can be done.




'Blockchain' is just a data structure.
But to give you a short anwser: Yes, it is possible to be implemented with an underlying blockchain in a decentralised way.




Altcoins(here: BTC forks) are based on bitcoin, not 'bitcoin core'.
Bitcoin core is just a client(full node / wallet) to access the bitcoin network.

But, no. I am not aware of an altcoin providing such a 'feature'.
What would be the sense of such a feature? What problem does it solve?

Since you are working on an immutable data structure the only way of accomplishing such an 'update' would be to reference to the old block/tx/message.
You approach should just work fine. That would have been my first approach too.

You just have to keep in mind that you still need verification (only poster of the first message can 'update' this message).

But note that the displaying of those messages (especially the updated messages) is done client-side.
It is definetely possible to see all old messages. The client has to be set up correctly and needs to have the blockchain synced and verified to display all messages/posts correctly.

Lets pretend the following:
Alice does post some text at block X.
Alice does edit this post at block X+10.

If Bob opens his clients and syncs, the moment he reaches block X, he will see the first post by Alice.
This will be the only message bob will see until he has synced up to block X+10.


Short answer: Yes, i think so.

To check whether your daemon is alive, does receive blocks, verifies them, etc... just look at the debug.log (standard directory on linux: ~/.bitcoin).
You will see relevant information regarding block count, transaction, .. , pebwindkraft's solution should be working for you.

If you want to check if RPC commands are working correctly (which they always should if your daemon is not corrupted), the only possibility i might think of is to code
a small script which does call the RPC commands regularly.

Generally, no.
Some forked coins may have the same API, but doesn't have to.
Just google "your_coins_name developer api" to find the correct API for your coin.




ERC20 tokens are just coded contracts. You may found them on github. This depends on the developer.
Regarding commands and deamon, look here.

You don't need to run a daemon for an ERC20 token. They run ontop of the ethereum network.
You might run an ethereum daemon if necessary.




ERC20 describes rather a standard for tokens, than a protocol.

This mostly sounds like a network issue (probably on myceliums's server side). This should be resolved within a day or two.
If you don't have time to (or don't want to) wait, you can always import your mnemonic seed into any BIP39 compatible wallet (e.g. electrum [1]).


The derivation path mycelium uses is: m/44'/0'/X'/Y/Z, where:
X = Number of your account (i.e. for the 1st created 'account' inside mycelium: 0; for the 2nd: 1, ...)
Y = 0 for receiving addresses; 1 for change addresses
Z = index of address (0 for first addres, 1 for second addres, ...).

So in electrum you have to enter:
m/44'/0'/0'/ for your 'first account',
m/44'/0'/1'/ for your second account, ...



[1] https://electrum.org/#home

walletnotify and blocknotify do run a script if a specific event happens.
You don't have to use a bash script. Python/PHP would work too, or any other scripting language.
But a script is needed.




If you specify the path like directory1/test.sh then it is a relative path (from where the executable is being started started (e.g. bitcoind folder)).
If you specify the path like /directory1/test.sh then it is an absolute path (from root folder).




IIRC you just have to use $transactionID = $1.

But i am not completely sure about that. It may also be $argv[1] or $argv[0](less probable, since this should be the command 'itself').

Routing system?  Mind explaining what you mean?




You have to specify the path to your script.
E.g. :

And inside your script.sh you can have the following:

%s (transaction ID) will be passed to your script and can be used/accessed via $1 (argv).


Note that walletnotify is called when:
1) You receive a transaction
2) You send a transaction
3) A (receiving) transaction gets the first confirmation

If you want to check for a further status (2+ confirmations), you have to use blocknotify instead of walletnotify.

You have to describe more detailed what exactly you want to achieve regarding privacy.

With core it won't be possible to see which transaction you have broadcasted.
If you broadcast a TX with core, it is just one between thousands (which you relay to other nodes). The receipent (1 hop away) can't tell for sure that you have broadcasted the TX. It could have been broadcasted by anyone, relayed by your node.

With electrum an attacker might be able (under some circumstances) to gather the IP of the broadcasting wallet (and therefore also your location; assuming no VPN/proxy is used).


You IP, however, will be visible to all nodes connected to your node. This is necessary.
Pretend you want to send a mail via snail-mail, but don't know the address. This doesn't work.
The only way to hide your IP is via using a VPN service (which will relay the traffic via their server to you; The IP of the VPN server will be visible to the network).


For a more detailed anwser, ask more detailed.

Generally you have to follow these steps:

• Open the wallet client on your PC (any client which supports hardware wallets; this can be the ledger chrome applications, electrum, altcoin-wallets with HW support, ..).
  
• Then connect and unlock (enter pin) your nano s
• Open the corresponding application (on your nano s)

Afterwards, your wallet (software on your PC) should show that it has found the nano s.

The exact process depends on the wallet you want to open. For BTC, follow HCP's description.

There is no the 'best' hardware wallet.

The most commonly used hardware wallets are from ledger (https://www.ledgerwallet.com/) and trezor (https://trezor.io/).
They are pretty much equally secure.

There are still differences between both wallets.
Trezor's model is a small mini computer. Ledgers nano s on the other hand is architectured 'around secure elements'.

The nano s does support more altcoins than trezor (and also seems to be adding new coins more frequently than trezor).

Ledger Nano S: https://www.ledgerwallet.com/products/ledger-nano-s
Trezor ONE/T: https://shop.trezor.io/

Any project (regardless whether open source or closed source) does rely on developer to enhance the project.
An open source project (e.g. bitcoin) does also rely on developer.

A lot of time has passed since the first version got released. A lot of good tweaks have been done

Where do you think do all of these improvements (e.g. segwit) come from? From independent developer.


There are even more enhancements coming (LN, Schnorr signatures, Coinjoin, ...). All from independend developer.

According to the official documentary of the bitcore.io libary (https://bitcore.io/api/lib/address#new_Address_new) the only way to create a nested P2SH address is to call new Address(data, network, [type]).

The function hdPrivateKey.derive(arg, hardened) seems to not be supporting nested P2SH. (https://bitcore.io/api/lib/hd-keys#HDPrivateKey+derive).

I might just not have found the correct function. But it seems that this is currently not possible with this libary 


Is there a specific reason you want to use javascript? This python libary does give you the ability to derive the desired P2SH address from your mnemonic seed.

What exactly did you do? Did you follow Lucius' post step-by-step?

Try the following (in this specific order):

• Close any ledger applicatoin running on your PC
• Disconnect your nano s
• Open the device manager (Windows-Logo -> 'device manager')
• Plug your nano s in
• Look at the device manager for a new device which just appeared (you may have to click 'reload' at the top bar). It should have a yellow exclamation mark
• Remove the device from the device manager
• Open ledger manager
• Connect your nano s / start the update again

Proof of Capacity (PoC) is not the same as Proof of Work (PoW). OP was mentioning PoW vs. PoS.
But this still doesn't mean that you can 'mine' with your HD.

It is more like staking your storage (e.g. lending to others). You are not actively using the space to calculate something.
Thats basically mining through 'staking storage'. Just like you can mine coin X by staking coin X for a timepsan of Y.

You can't mine with a HDD. Neither with RAM only.
A HDD does store data. It does NOT calculate anything. Particularly it is not possible to calculate hashes on an HDD.
The same does apply to RAM. Thats 'just' memory.




This CAN lead to more centralisation than POW, but doesn't have to.
It doesn't really matter whether you stake an insane amount of money to get a big % of the total hashrate or just buy an insane amount of ASICS (for an insane amount of money) to gain the same big % of the hashrate.

There are several meanings of 'token':

• The term token is used in a very general sense to describe any digital asset (where Bitcoin is a token and Ether is a token).
• The term token is used to describe a unit of value (I have X Bitcoin tokens). Here it refers to the fact that cryptocurrencies, like the U.S. dollar, are value tokens / currency tokens / token money (they represent value, but aren’t themselves of any inherent value)
• Meanwhile, sometimes when people say “token” they are specifically referring to digital assets that are built on another cryptocurrency’s platform like Ethereum’s ERC-20 tokens. The native token on the Ethereum platform is Ether, KIN for example is a ERC-20 token created from the KIN ICO. Both Ether and KIN are cryptocurrencies (AKA tokens) on the Ethereum network, but one might refer to KIN as “a token” to differentiate it from cryptocurrencies that use their own platform / network / blockchain.
• Token can also be used to describe “utility tokens” which are tokens that can be used for specific functions in specific systems (such as a token that lets you access a certain amount of cloud storage).
  

Source: https://cryptocurrencyfacts.com/what-is-a-cryptocurrency-token/ (<-- Does explain tokens very well, might be worth a read for you)


In most cases 'token' refers to an ERC-20 token (built on top of ethereum) following the ERC-20 standard.
   



No. The smallest fraction of a bitcoin is a satoshi. 1 satoshi = 0.00000001 BTC.




No. These are simple UTXO's.




This most probably means that a foundation/company/developer/founder of token X has released tokens.
This includes any possible distribution (e.g. aidrop, token sale, ..). This means they have been brought into circulation.

What kind of monitoring are you thinking about?

You can either connect via an RPC port and code a small script which polls the information you want to check.
This includes network information (e.g. connected peers, new blocks, transactions, ...).

Or you can monitor the output of the log file.
Either check the debug.log from bitcoin core (standard directory: ~/.bitcoin) or the system log (/var/log/syslog).

This mainly depends on what exactly you want to monitor.

No. An replay attack is a scenario where an attacker takes your transaction from one chain and broadcasts it into another chain (which does have the same address format).
This was the case when btrash bcash forked. They did not change anything in the address-/transaction format allowing tx's to be replayed on the other chain.
Fortunately replay protection has been implemented already.

More information about an replay attack (generally in networks): https://en.wikipedia.org/wiki/Replay_attack
More information about an replay attack (related to bitcoin): https://coinsutra.com/what-are-replay-attacks/ or https://themerkle.com/what-is-a-bitcoin-replay-attack/

This should fix it. Just a small correction:
The nano s has to be plugged in to appear in the device manager. Afterwards the device will be shown with the yellow exclamation mark.

This bug does occasionally occur on windows devices.