First of all thanks for your replies. Keep it up!
 I need more advice and I'll try to be more specific.

The focus here is to describe the state of the art on both sides: from a chainanalysis perspective analyzing the tools and on the other side the regulators, law enforcement, etc.
I know that many companies have developed proprietary tools.
AFAIK chainanalysis is not performed on a blockchain, it's too slow and inefficient. GraphDB or other NoSQL DBs in synch with the blockchains are used to achieve a higher level of efficiency. 
Are there some papers, research, github repo, tutorials, speeches, ... to deepen my knowledge?
I don't deny that my final aim would be to propose the content for a chainanalysis course.
What would be in your opinion the structure of such course?

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.

Could you please make an example on how to manage a cold wallet and a hot wallet created with disableprivatekeys set?

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 https://bitcoinelectrum.com/creating-a-watch-only-wallet/.

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

I just upgraded from the previous release and checked some APIs.
Could the warning at the bottom be somehow related to the upgrade?


$ bitcoin-cli -testnet getblockchaininfo | jq
{
  "chain": "test",
  "blocks": 1764143,
  "headers": 1764143,
  "bestblockhash": "00000000514399503aca1bffa0bc329646e54aaccdf439093c80b00b6fc87afb",
  "difficulty": 1,
  "mediantime": 1591701573,
  "verificationprogress": 1,
  "initialblockdownload": false,
  "chainwork": "00000000000000000000000000000000000000000000015bbaaea736421238f7",
  "size_on_disk": 27411014312,
  "pruned": false,
  "softforks": {
    "bip34": {
      "type": "buried",
      "active": true,
      "height": 21111
    },
    "bip66": {
      "type": "buried",
      "active": true,
      "height": 330776
    },
    "bip65": {
      "type": "buried",
      "active": true,
      "height": 581885
    },
    "csv": {
      "type": "buried",
      "active": true,
      "height": 770112
    },
    "segwit": {
      "type": "buried",
      "active": true,
      "height": 834624
    }
  },
  "warnings": "Warning: unknown new rules activated (versionbit 28)"
}

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

Good points.
Regarding when and where I meant that if the parties have to meet to sign the agreement and perform the transaction right away, the location and date (especially in case of a high amount) must be kept confidential.

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.

It's the other way around. Think about it:
No bitcoin or no cryptocurrency means => no asset available to reward miners => No miners means => Official validators required
But this means that we're turning around in circles back to a Central authority that provides governance!
Another question is why should appointed validators use a blockchain when they're the only ones authorized to validate blocks?
Why all the effort to mine and give PoW to themselves?

Interesting, can you share some details?
Have you used a RDBMS like MySQL or similar?
Have you had any issues importing the blockchain in the DB?   
What did you do it for? Did you discover something interesting?

Please share.

I would say the first example is more suitable but at the moment I'm not going to build a tools I'd rather like to understand the theory and the approach. Any suggestion?

IMHO I do not see it hard to achieve the second result ... scheduling a blockchain analyzer could be enough at a first stage.

BTW my request could be somehow related to this post (but it's much more generic) https://bitcointalk.org/index.php?topic=267618.0

Thanks for all the links. Browsing around I've already ran across https://www.chainalysis.com/ but unfortunately it's a product. What I'm looking for are tutorials, documents, scientific papers (maybe based on graph theory) that can explain me the basis of chain analysis and then decide if it's worthwhile to dive more deep into the subject.
If you think about use cases it may have the potential to become a new branch of computer forensics.

You're not relying on a centralized service but on a SC (decentralized) developed by a centralized service provider (i.e. airline company). The benefit is that the SC acts as an escrow. The airline company will be fully paid if the flight lands within the time interval otherwise the client will be automatically refunded (no forms to fill, no requests to submit, ...). In addition the SC is censorship resistant, no one can modify or cancel it.

https://en.wikipedia.org/wiki/Graph_database
In order to perform an analysis you must have the right tools. Actually it's not just tables and columns if you compare graph to relational databases. They have been designed for different scopes.

There are some classical examples:
- An airline company that sells tickets online through a smart contract. The client will be refunded by x% if the flight departs or arrives at destination with more than n hours delay.
- A farmer buys an insurance to cover him from bad weather. If the minimum temperature from dayStart to dayEnd will be more than n day below zero degrees C the farmer will cash a certain amount.

As you can see the above examples relies on Oracles in charge to update the "Virtual world" with data coming from the "Real world". And that's another great subject to debate.

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.

Yes I know, but I meant only segwit. I know Core is not supporting 2x.
So which is the first version released by Core with segwit? 
Same thing for comparison schema or slide ... are there some pictures showing block data structure and verification rules changed before and after segwit?
Thanks.

Cool, thanks for your reply.
When has it been released? I've compared bitcoin core 0.15.0.1 with 0.14.1 and MAX_BLOCK_WEIGHT (should be the right constant to check) is the same.
Does anyone know where to find a document, pdf, slides, ... with a graphical comparison schema of the differences before and after segwit?

Thanks anonymoustroll420 and achow101 for your replies.
@anonymoustroll420: strictly speaking it is not a blocksize increase. Stuff has been moved in another place to make room for other transactions.
As far as I know blocksize is the same and that's the reason for "2x or not 2x". But this is another story.

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.