It's a controversial topic and I'd like to dig more into it, to understand the current state of the art in terms of tools, processes and outcomes.
It's clear that the level of transparency in some blockchains like Bitcoin is more a bug than a feature.
I need your help to collect as many info as possible for an university assignment: tools, github repos, papers, websites, services, ...

Thank you.

The purpose of this feature as explained here: https://github.com/bitcoin/bitcoin/pull/9662 should be to ensure no mix between hot and cold keys but honestly I don't understand the use case.
What I've used instead, is the watch-only deterministic wallet created using a Master Public Key as explained here: https://bitcoinelectrum.com/creating-a-watch-only-wallet/.

Can anyone explain how to use createwallet "disableprivatekeys" together with fundrawtransaction?

I've searched in the forum using the terms in the subject with no success (too generic and between quotes there are no matches)
It doesn't seem to be a specific section either.
Can anyone address me to some technical link, tutorial, discussion, ... ?
tnx

Please help me to list the best security practices implementation details of my assignment.

Alice and Bob sign an agreement.
Alice borrows Bob $8,000 (assuming that 1 BTC = $8,000) for a period of time T and Bob put up a collateral of 1.5 BTC into a multisig account.
If within time T Bob settles his debt ($8,000 + fees) then Bob can have 1.5 BTC back, else Alice can seize 1.5 BTC collateral and do whatever she wants.

Here's an example by Gavin Andresen that can be used for what's described above:
https://gist.github.com/gavinandresen/3966071

Here is what I've pointed out so far:

- How to create the three keypairs and give the private keys of the multisig addresses to three different Escrow agents in such a way that the private keys are not revealed to anyone (even the creator)?
- After Bob performs the transaction from his wallet to the multisig address wait for 6 confirmations before lending him $8,000.
- Reveal operation's details (when and where) only to people involved.
- What's best cold storage method with pros and cons? (i.e. HW wallets: if the period T is relatively long, new firmware may be released to patch vulnerabilities. An update process needs to be defined)
- Transfer 1,5 BTC to either Alice or Bob according to agreement outcomes. Is this probably the least risky step in the list?

Something is missing for sure ...

UPDATE:
- send transactions to your fullnode or to verified peers.

AFAIK it all starts from importing a blockchain into a graph database, then you can start analyzing behavioral patterns, relations between addresses, ...
Does anyone know where can I get further info regarding this subject?
What will be the impact of this analysis with the rise of LN, sidechains and other anonymity solutions?
Thanks.

I have read that Segwit is a necessary condition for lighting network. In other works LN cannot be released without Segwit.
Where can I find a technical explanation about this?
Thanks.

Can anyone please tell me where the heck is the maximum block size (1M) defined and where it is used in the code to check? Thanks.