Update to only use lisk-sdk

Expected behavior

lisk-core should be able to be built only using lisk-sdk.

Actual behavior

It uses multiple packages. @liskhq/lisk-cryptography @liskhq/lisk-transactions etc

Which version(s) does this affect? (Environment, OS, etc…)

2.0-

[michielmulders]

@shuse2 comment: It’s because SDK is in javascript. It’s not creating this link to the lisk-transactions. If we use directly from SDK, it doesn’t know about the lisk-transactions in Typescript way.

[michielmulders]

If you compare the exported interface of tx and crypto. crypto: node_modules/@liskhq/lisk-transactions/dist-node/index.d.ts

import * as constants from './constants';
export * from './buffer';
export * from './convert';
export * from './encrypt';
export * from './hash';
export * from './keys';
export * from './sign';
export { constants };

–> All public interfaces are exported.

tx: node_modules/@liskhq/lisk-transactions/dist-node/index.d.ts

import * as BigNum from '@liskhq/bignum';
import { transfer } from './0_transfer';
import { TransferTransaction } from './0_transfer_transaction';
import { registerSecondPassphrase } from './1_register_second_passphrase';
import { SecondSignatureTransaction } from './1_second_signature_transaction';
import { DelegateTransaction } from './2_delegate_transaction';
import { registerDelegate } from './2_register_delegate';
import { castVotes } from './3_cast_votes';
import { VoteTransaction } from './3_vote_transaction';
import { MultisignatureTransaction } from './4_multisignature_transaction';
import { registerMultisignature } from './4_register_multisignature_account';
import { createDapp } from './5_create_dapp';
...

–> Only few public interfaces are exported. The issue happens because we use types that are not exported as input for certain functions that are exposed.