bitpay / bitcore-wallet Goto Github PK

➜  bitcore-wallet git:(master) bin/wallet-import

  Usage: wallet-import [options] <backup> <passphrase>

  Options:

    -h, --help                       output usage information
    -V, --version                    output the version number
    -f, --file <filename>            Wallet file
    -h, --host <host>                Bitcore Wallet Service URL (eg: http://localhost:3001/copay/api
    -v, --verbose                    be verbose
    -t, --testnet                    testnet network
    -f, --file                       import from file
    -q, --qr                         import from a QR code
    -e, --exportpassword <password>  a password to decrypt the data being imported
    -p, --password                   Encrypt wallet. Will ask password interactively

--file/-f is used twice

Hi,

I created a 2-3 wallet using bitcore-wallet 0.0.7. Tried to join it with Copay wallet 1.2.5 but following error appears:
'Could not join wallet: The wallet you are trying to join was created with an older version of the client app.'

Any help appreciated!

There should be an arg for setting the fee.

Bitcore Wallet Service seems to support multiple_outputs which seems to be counterpart of sendmany in bitcoin-cli. Source: https://github.com/bitpay/bitcore-wallet-service/blob/master/lib/model/txproposal.js

Please implement wallet-sendmany command-line tool.

./wallet confirm -h

/Users/matiaspando/dev/bw/node_modules/bitcore-wallet-client/lib/api.js:84
this.basePath = this.baseUrl.replace(/http.?://[a-zA-Z0-9:-]*//, '/');
^
TypeError: Object true has no method 'replace'
at new API (/Users/matiaspando/dev/bw/node_modules/bitcore-wallet-client/lib/api.js:84:32)
at Function.Utils.getClient (/Users/matiaspando/dev/bw/bin/cli-utils.js:52:16)
at Object. (/Users/matiaspando/dev/bw/bin/wallet-confirm:11:7)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:906:3

Here's a pasta of my status message:

* Wallet Mwallet [testnet]: 2-of-2 complete
* Copayers: Mona, guest
* Balance 119,900 bit (Locked: 100,000 bit)
* TX Proposals:
        346f ["okuruyo, message test" by Mona] 10,000 bit => mz3QPobkXVRtyMZ7D1pU65hEbCDbUeYJ9K
                Actions:  Mona ✓
                Missing signatures: 1

Hi,

I would like to try out the v8.0.0 branch, but I have trouble getting it to work.

When I checkout the branch and run npm install, I get the error

npm ERR! code ETARGET
npm ERR! notarget No matching version found for [email protected]
...

I tried checking out the v8.0.0 branch of bitcore-wallet-client and link to it using npm link (and subsequently doing the same for bitcore-mnemonic). After that, npm install worked, but then I get the error

More than one instance of bitcore-lib found.
Please make sure to require bitcore-lib and check that submodules do
not also include their own bitcore-lib dependency.

when trying to run the wallet command.

Any hints about how I'm to supposed to run it instead?

So I've been playing around with this here. Very interesting stuff you have going on here.

But here's the problem. The command cd bin returns nothing once we've created bws. I even went and looked in my /usr/bin files and there is no wallet command. Perhaps there was something else you meant to put down for the instructions? In addition, trying to run the start script again gives me this error:

vor0220@vor0220-ubuntu:~/BitcorePlayground/bws$ node start
module.js:340
    throw err;
      ^
Error: Cannot find module '/home/vor0220/BitcorePlayground/bws/start'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Function.Module.runMain (module.js:503:10)
at startup (node.js:132:16)
at node.js:817:3

Hi,

I created a 2-3 wallet with bitcore-wallet 0.0.7. Using it with bitcore-wallet-client 0.6.0 to propose a transaction, but receiving the SERVER_COMPROMISED error code when I do so. Using the public bitcore wallet service by Bitpay.

Also see: bitpay/bitcore#1341 where I originally was using bitcore-wallet-client 0.1.3, but now upgraded.

I think it is a version incompatibility. Which version work for sure? With testnet everything was working fine before.

Thank you for helping!

$ ./wallet derive --help

var Bitcore = require('bitcore-wallet-client').getBitcore();
^

TypeError: require(...).getBitcore is not a function
at Object. (5:48)
at Module._compile (module.js:410:26)
at Object.Module._extensions..js (module.js:417:10)
at Module.load (module.js:344:32)
at Function.Module._load (module.js:301:12)
at Function.Module.runMain (module.js:442:10)
at startup (node.js:136:18)
at node.js:966:3

hi there,

I saw there are two Utils.UNITS in cli-utils.js (see [2] and [3]) which acutally cause troubles when determining rate at [1].

var rate = Utils.UNITS[unit];

which requires a number not a structure as you specified here:

Utils.UNITS = {
  btc: {
    name: 'btc',
    toSatoshis: 100000000,
    maxDecimals: 8,
    minDecimals: 8,
  },
  bit: {
    name: 'bit',
    toSatoshis: 100,
    maxDecimals: 2,
    minDecimals: 2,
  },
};

I don't know which one you are going to keep, but I am sure that not the both.

[1] https://github.com/bitpay/bitcore-wallet/blob/master/bin/cli-utils.js#L241
[2] https://github.com/bitpay/bitcore-wallet/blob/master/bin/cli-utils.js#L260
[3] https://github.com/bitpay/bitcore-wallet/blob/master/bin/cli-utils.js#L222

It is a testnet 1-1 wallet.

$ wallet import backup.dat

* Saving file /Users/gustavo/.wallet.dat

/Users/gustavo/Documents/github/bitcore-wallet/bin/wallet-import:35
    var access = client.canSign() ? 'with signing capability' : 'without signi
                        ^
TypeError: Object object has no method 'canSign'

The file .wallet.datis OK.

wallet status

* Wallet BLA [testnet]: 1-of-1 complete 
* Copayers: gus
* Balance 0 bit (Locked: 0 bit)

WBS was started, and email server and notification server not started

i tried this commend today ....

./wallet create 'my wallet' 2-2 -t

it gives me error but this same command worked 2 day before

!! Error: WALLET_BUSY: Wallet is busy, try later

Why This happening ??

Hi,

Is this supposed to work?
I managed to create a 2-2 testnet wallet. I used copay-web as my spouse.
wallet creation completed just fine.

Now, when I create a txproposal from the copay-web and ask for txproposals I get:
{ code: 'SERVERCOMPROMISED',
message: 'Server sent fake transaction proposal' }

If I try to send money using the CLI I get:

[error] <ClientError:BADREQUEST Invalid proposal signature>
{ code: 'BADREQUEST', message: 'Invalid proposal signature' }

What am I doing wrong?

Please note that I'm new to NODE so don't know how to provide more information about the environment.
BTW - is there a java api available?

Thanks

Rather than a binary solution:
EITHER enter password for EVERYTHING or NOTHING

I would suggest 3 methods.

1. Full encryption. All commands require password.
2. Partial encryption. Only private key related commands require password.
3. No encryption. No password required.

When you create a tx proposal it returns

• Tx created: ID 01425567324953079daf0f-00b9-49af-bbb8-63490bfdc453 [pending] RequiredSignatures: 1

But when you list the tx proposals it returns

• TX Proposals:
  c453 [ by user3] 5,000 bit => 2N1fgfx4y8FaZKpLJL2qXw2DLQzDsf2pzXr
  Missing signatures: 1

I think I should be always c453

Hi,

I'm getting the below error for my 2-4 wallet.
Getting the same error also with the CoPay app (haring the same wallet):

C:\workspace_sts\bitcore-wallet\bin>node wallet status
[error] [object Object]
{ code: 'ERROR',
error: 'Could not fetch unspend outputs:[object Object]' }

Thanks

Offer

./wallet confirm -f

fs.js:429
binding.open(pathModule._makeLong(path),
^
TypeError: path must be a string
at Object.fs.open (fs.js:429:11)
at Object.fs.readFile (fs.js:206:6)
at FileStorage.load (/Users/matiaspando/dev/bw/bin/filestorage.js:20:11)
at Function.Utils.getClient (/Users/matiaspando/dev/bw/bin/cli-utils.js:57:11)
at Object. (/Users/matiaspando/dev/bw/bin/wallet-confirm:11:7)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)

this is not 100% accurate. It should be noted that wallet.dat is already complete and it is all it is needed for recover the wallet.

TypeError: http[fn] is not a function
at PayPro._nodeRequest ( node_modules/bitcore-wallet-client/lib/paypro.js:17:11)

not an issue just a question, and please forgive my ignorance...

do i need to run a full node with BWS installed to run bitcore-wallet? it's looking like $160 a month with digital ocean for enough ssd to run a full node... or can it talk to a bitpay bitcore node with BWS?