Hi! I am looking into this library for a project that I am working on and I have two questions.

First of all... I was looking at the example and I noticed that the library is making calls to http://btc-testnet.horizontalsystems.xyz/apg. Can somebody tell me why and if it is possible to easily remove these calls? If not at least give me some details on what is returned so we can maybe replace it with our own backend.

The second one is more complicated. Our client is developing a hardware wallet and for us to successfully implement support for that we need to get access to the low level transaction data that we can then send to the device for signature. My question is - how hard would it be to modify this library so it could be initialized without mnemonics/seed (so in "read only" mode) and modify it to get access to the raw transaction data so that the hardware device can provide the signature instead? And of course any tips on where I should look to do this.

Bug: When creating or importing wallet on a build created in XCode 11.1 for iOS 13, there is an internal error.

Logs are:

2019-10-22 20:29:59.754208+0700 Runner[23362:1875929] *** Terminating app due to uncaught exception 'RLMException', reason: 'Primary key property 'reversedHeaderHashHex' does not exist on object 'Block''
*** First throw call stack:
(
	0   CoreFoundation                      0x00007fff23baa1ee __exceptionPreprocess + 350
	1   libobjc.A.dylib                     0x00007fff50864b20 objc_exception_throw + 48
	2   Realm                               0x000000010d4d7433 +[RLMObjectSchema schemaForObjectClass:] + 4371
	3   Realm                               0x000000010d5e3d9e _ZL16RLMRegisterClassP10objc_class + 302
	4   Realm                               0x000000010d5e4807 +[RLMSchema sharedSchemaForClass:] + 119
	5   Realm                               0x000000010d4cf623 +[RLMObjectBase sharedSchema] + 67
	6   Realm                               0x000000010d4cce3b _ZL33maybeInitObjectSchemaForUnmanagedP13RLMObjectBase + 123
	7   Realm                               0x000000010d4ccd5d -[RLMObjectBase init] + 125
	8   RealmSwift                          0x000000010ea8f061 $s10RealmSwift6ObjectCACycfc + 65
	9   RealmSwift                          0x000000010ea8f0f3 $s10RealmSwift6ObjectCACycfcTo + 19
	10  HSBitcoinKit                        0x000000010cd87c94 $s12HSBitcoinKit5BlockCACycfc + 916
	11  HSBitcoinKit                        0x000000010cd87d43 $s12HSBitcoinKit5BlockCACycfcTo + 19
	12  HSBitcoinKit                        0x000000010cd872bb $s12HSBitcoinKit5BlockC10withHeaderAcA0cE0CSg_tc33_F6AB7670EFC3EF947452E2B35A3BBCA6LlfC + 155
	13  HSBitcoinKit                        0x000000010cd87607 $s12HSBitcoinKit5BlockC10withHeader6heightAcA0cE0C_SitcfC + 87
	14  HSBitcoinKit                        0x000000010cd848c0 $s12HSBitcoinKit14BitcoinTestNetC16validatorFactoryAcA015IBlockValidatorG0_p_tcfc + 800
	15  HSBitcoinKit                        0x000000010cd8453f $s12HSBitcoinKit14BitcoinTestNetC16validatorFactoryAcA015IBlockValidatorG0_p_tcfC + 63
	16  HSBitcoinKit                        0x000000010cd767ea $s12HSBitcoinKit07BitcoinB0C9withWords4coin8walletId9newWallet22confirmationsThreshold11minLogLevelACSaySSG_AC4CoinOSSSbSiAA6LoggerC0O0Otcfc + 2522
	17  HSBitcoinKit                        0x000000010cd75dad $s12HSBitcoinKit07BitcoinB0C9withWords4coin8walletId9newWallet22confirmationsThreshold11minLogLevelACSaySSG_AC4CoinOSSSbSiAA6LoggerC0O0OtcfC + 141
	18  bitcoin_wallet                      0x000000010f096d59 $s14bitcoin_wallet24SwiftBitcoinWalletPluginC06importE033_567BEF0ED0D1A5D26F8F5D89B0099DFALL5words8testMode0B2IdySaySSG_SbSStF + 329
	19  bitcoin_wallet                      0x000000010f09887f $s14bitcoin_wallet24SwiftBitcoinWalletPluginC6handle_6resultySo17FlutterMethodCallC_yypSgctF + 5487
	20  bitcoin_wallet                      0x000000010f09c73b $s14bitcoin_wallet24SwiftBitcoinWalletPluginC6handle_6resultySo17FlutterMethodCallC_yypSgctFTo + 139
	21  Flutter                             0x000000010ad314fd __45-[FlutterMethodChannel setMethodCallHandler:]_block_invoke + 104
	22  Flutter                             0x000000010accaec0 _ZNK7flutter21PlatformMessageRouter21HandlePlatformMessageEN3fml6RefPtrINS_15PlatformMessageEEE + 166
	23  Flutter                             0x000000010acce780 _ZN7flutter15PlatformViewIOS21HandlePlatformMessageEN3fml6RefPtrINS_15PlatformMessageEEE + 38
	24  Flutter                             0x000000010ad2bdb3 _ZNSt3__110__function6__funcIZN7flutter5Shell29OnEngineHandlePlatformMessageEN3fml6RefPtrINS2_15PlatformMessageEEEE4$_31NS_9allocatorIS8_EEFvvEEclEv + 57
	25  Flutter                             0x000000010acdd3f1 _ZN3fml15MessageLoopImpl10FlushTasksENS_9FlushTypeE + 123
	26  Flutter                             0x000000010ace2742 _ZN3fml17MessageLoopDarwin11OnTimerFireEP16__CFRunLoopTimerPS0_ + 26
	27  CoreFoundation                      0x00007fff23b0d994 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
	28  CoreFoundation                      0x00007fff23b0d682 __CFRunLoopDoTimer + 1026
	29  CoreFoundation                      0x00007fff23b0ccda __CFRunLoopDoTimers + 266
	30  CoreFoundation                      0x00007fff23b07a4e __CFRunLoopRun + 2238
	31  CoreFoundation                      0x00007fff23b06e66 CFRunLoopRunSpecific + 438
	32  GraphicsServices                    0x00007fff38346bb0 GSEventRunModal + 65
	33  UIKitCore                           0x00007fff47578dd0 UIApplicationMain + 1621
	34  Runner                              0x000000010a49b0c8 main + 72
	35  libdyld.dylib                       0x00007fff516ecd29 start + 1
	36  ???                                 0x0000000000000001 0x0 + 1
)
libc++abi.dylib: terminating with uncaught exception of type NSException
(lldb) 

main point

Terminating app due to uncaught exception 'RLMException', reason: 'Primary key property 'reversedHeaderHashHex' does not exist on object 'Block''

Reason: The reason is that Realm old versions don’t work with XCode 11 well.

Our dependencies list are

- Alamofire (4.8.2)
- BigInt (3.1.0):
  - SipHash (~> 1.2)
- bitcoin_wallet (0.0.1):
  - Flutter
  - HSBitcoinKit
- Flutter (1.0.0)
- HSBitcoinKit (0.4.1):
  - Alamofire (~> 4.8.0)
  - BigInt (~> 3.1.0)
  - HSCryptoKit (~> 1.1.0)
  - HSHDWalletKit (~> 1.0.3)
  - ObjectMapper (~> 3.3.0)
  - RealmSwift (~> 3.11.0)
  - RxRealm (~> 0.7.0)
  - RxSwift (~> 4.0)
- HSCryptoKit (1.1.0)
- HSHDWalletKit (1.0.3):
  - HSCryptoKit (~> 1.1.0)
- ObjectMapper (3.3.0)
- Realm (3.11.2):               <--- PROBLEM
  - Realm/Headers (= 3.11.2)
- Realm/Headers (3.11.2)
- RealmSwift (3.11.2):
  - Realm (= 3.11.2)
- RxRealm (0.7.6):
  - RealmSwift (~> 3.0)
  - RxSwift (~> 4.0)
- RxSwift (4.5.0)
- SipHash (1.2.2)

We can see that HSBitcoinKit depends on Realm with wrong version.

Right Realm version which supports XCode 11 is about 3.18+ (as said here https://github.com/realm/realm-cocoa/issues/6163)

I checked HSBitcoinKitrepository and didn’t found any Realm dependencies. After some research, I found that it was there but was deleted here https://github.com/horizontalsystems/bitcoin-kit-ios/commit/65a13b21dff97b767c229489ea48639a773d5247#diff-691ea2c5e475d83f07d8cf1313fe74ec, and the fresh version of HSBitcoinKit doesn’t have Realm dependency at all.

This is strange because we have the latest version of HSBitcoinKit installed. Turns out that version in their repository (0.8.0) differs from the version on CocoaPods (0.4.1.).

You guys didn’t upload the last version to the pods!
Could you please do it?

Thanks a lot!

Hi! I was wondering if it is okay that the syncing progress takes long now? it used to be way shorter 2 days ago, did something change? also, it seems when you're trying to send a transaction now, it keeps failing due to it is always getting blocks over and over, until it stabilizes for a little bit and you can send it then it goes back to fetching blocks, which is also something that wasn't happening that constantly 2 days ago, just little observations I've noticed since the last time I've been using the library, I've been pretty much studying the library by looking through your demo project but it also takes longer to sync now and to send transactions it's a little unstable since it always keeps fetching blocks sometimes on your demo project too

Hi. Thank you for your work, this is a great project and it will be more than useful if I can implement this to my project. i am having a lot of stupid errors while trying to start the project. I am currently on M1 Pro chip, with Xcode 13.3. I keep getting a lot of errors. And when I fix those, new ones appear. I got other types of errors on an other git NFT Eth project too, I think it has to do something about my MacBook 2021 16inch. I am leaving an image of one of the many errors I get. And I do not use the simulator, I am aware of the arm64 thing. if you have in hand a Mac with m1 chip can you verify that there are no problems with the project and you can download the zip, pod install, and start the app? thank you.

Hi

I cannot send Bitcoin in TestNet

let transaction = try kit.send(to: wallet, value: 1000, feeRate: 70, sortType: .none) I receive BitcoinCoreErrors.SendValueErrors.singleNoChangeOutputNotFound

the balance: 0.0005 BTC

BitcoinKit: 0.15.4 Xcode Version: 13.2 Swift Version: 13.0

Am using BitcoinKit 0.17 in test net. I've sent 0.00083 tBTC to my wallet (https://blockstream.info/testnet/tx/b95235c6c2224f987f2cbb40cf04ba934ba4b2eac3ef42a890f8e2a3c4ca4087). After receiving the tx balance was correct, my receive address changed, but after 3 days all of a sudden my receive address reverted to a previously used for the incoming tx and frameworks shows a wrong balance of the wallet (0). Also TransactionRecord of the incoming tx doesn't recognise the tx output as mine anymore (output.mine is false). BitcoinKit syncing with peers without any noticeable issues. Is there a way to reset kit state, so it's recognise the tx output as mine and got the correct balance? Any suggestions are welcome.

@esen @mNizhurin @ant013 Hi, Awesome @horizontalsystems team! I wanna add some altcoins here. But I wonder how can I define checkpoint files for them. Could you have a chance to tell me?

When loading a wallet from an existing seed, after API syncing, the balance is not recovered (displayed as 0).

Tested on:

• network: Testnet
• coin: BTC
• address type: Bech32 (.bip84)

Hello! I was wondering if you are able to have multiple accounts in the HDWallet BIP44 implementation (perhaps this question may sound dumb as I'm not 100% sure how things work)

root -> BIP44 -> coinType 0 -> account 0 -> chain 0 -> then N addresses here

That'd be to store bitcoin in account 0 right? is it possible to then derivate to account 1 in a way that

root -> BIP44 -> coinType 0 -> account 1 -> chain 0 -> again N addresses here

in the library so you would have 2 bitcoin accounts in the HDWallet? is there a way to just get the balances and transactions of account 0, then of account 1 individually I don't know if the question is being asked properly or if is not the way BIP44 is supposed to be intended just wondering if I wanted to have 2 bitcoin wallets I'd have to create another 12 word list mnemonic right? or there is a way to have 2 bitcoin wallets in the same HDWallet? Thanks in advance and I'm sorry if the question wasn't being asked properly, I've been learning a lot about crypto development thanks to all of you. Kudos and have a great day/night!

First of all I'd like to thank for your brilliant work on the library! <3

Am having an issue syncing a new wallet in TEST NET. InitialSyncer return an error on single.subscribe:

invalidResponse(statusCode: 404, data: Optional({
    error =     {
        message = "Not found.";
    };
}))

18:40:41.173 ❤️ ERROR  apiSync: invalidResponse(statusCode: 404, data: Optional({
    error =     {
        message = "Not found.";
    };
}))

Previously created wallets syncing with peers just fine as well as syncing new wallet on MAIN NET. Currently as a workaround I comment out initial syncer and syncing a new wallet with peers, however syncing takes significant more time. Any advices how to sync a new wallet in TEST NET?

Am using BitcoinCore and BitcoinKit ver 0.17. The issue started no more than couple of weeks ago, previously initial syncer worked without issues.

Thanks!

let mnemonic = Mnemonic.seed(mnemonic: words)

do {
    let bitcoinKit = try BitcoinKit(withWords: words, bip: .bip44, walletId: "bitcoin-wallet-id", syncMode: .api, networkType: .testNet)
    
    print("address", bitcoinKit.receiveAddress())
    //bitcoinKit.start()
    bitcoinData = bitcoinKit
    
    let wallet = HDWallet(seed: mnemonic, coinType: .zero, xPrivKey: .init(), xPubKey: .init())
    let path = "m/44'/1'/0'/0"
    let privateKey = try wallet.privateKey(path: path)
    
    let testKey = try wallet.privateKey(account: .zero, index: .zero, chain: .external)
    print("myPrivateKey1", testKey.raw.base64EncodedString())
    
    let publicKey = try bitcoinKit.receivePublicKey()
    print("publicKey", publicKey)
    
    
} catch (let err) {
    print("err occ", err)
}

}

Hello, im facing Issues with with connecting to Testnet via Alamofire.

Error:

ERROR : API IN: POST https://btc-testnet.horizontalsystems.xyz/api/tx/address
noResponse(reason: Optional("Session was invalidated without error, so it was likely deinitialized unexpectedly. Be sure to retain a reference to your Session for the duration of your requests."))

Code:

    func checkbalance(){
        
        print("CheckBalance start");
        
        let bitcoinKit: BitcoinKit
    
        let words = [Safety wise]
    
        bitcoinKit = try! BitcoinKit(withWords: words, bip: .bip44, walletId: "bitcoin-wallet-id", syncMode: .api, networkType: .testNet, logger: .none)

    
        bitcoinKit.start()
        
        
        print(bitcoinKit.receiveAddress())
        
        print(bitcoinKit.balance)
        
        print(bitcoinKit.statusInfo)
        
        try? bitcoinKit.send(to: "mrjQyzbX9SiJxRC2mQhT4LvxFEmt9KEeRY", value: 1000, feeRate: 10000, sortType: .none)
        
        
        print("BTC session completed!")
        
        
        bitcoinKit.stop()
    
    }

Thanks for Help!

Does anyone have an idea why this transaction would return Unknown address for the from address.

I've seeing this behaviour before while running on testnet, and assumed it was related to that. But now I'm seeing this happening on mainnet.

https://live.blockcypher.com/btc/address/bc1qf0w93ddyuc8l2hc3ls9myxuxqqht375szse502/

I have a Dash wallet that stops the synchronisation when it arrives to this transaction

https://blockchair.com/es/dash/transaction/3cc6e81dbb258a6fb88fb46e35b0a8e6e6c77fd4699d4a8100b9c700a5a7b3de

This transaction comes from Dash masternode, and it has a coinbase input, I believe that DashKit doesn't support this type of inputs and it gets stuck in an infinite loop.

https://dashcore.readme.io/docs/core-ref-transactions-raw-transaction-format#coinbase-input-the-input-of-the-first-transaction-in-a-block

Good day

kit = try BitcoinCashKit( withWords: words, walletId: "bitcoin-cash-wallet-id", syncMode: .api, networkType: networkType, confirmationsThreshold: 1, logger: .init(minLogLevel: .error) )

in func kitStateUpdated(state: BitcoinCore.KitState) I receive the error

URLSessionTask failed with error: A server with the specified hostname could not be found.