Search content
Sort by

Showing 16 of 16 results by Undecidable
Post
Topic
Board Electrum
Re: lost my seed and 2fa electrum wallet
by
Undecidable
on 24/06/2017, 20:49:55 UTC
Try contacting Trustedcoin support https://api.trustedcoin.com/#/contact-us
Post
Topic
Board Electrum
Re: Invalid OTP
by
Undecidable
on 03/11/2016, 06:25:09 UTC
Well, one of my saved seeds is 12 words and it restores just fine, the thing is that wallet balance is 0. I have another seed saved and it has 16 words, I try to restore it and when I enter the seed, the "Next" button is greyed out and cant click it to continue.

Electrum 2FA seeds have never been 16 words long.   AFAIK they've only ever been 24 words (super old versions), 25 words (versions before 2.7) or 12 words (2.7+) .   

I suspect the mnemonic you are trying to enter is from some other application?
Post
Topic
Board Electrum
Re: Electrum 2.7.9 Error -> Invalid transaction: invalid signature
by
Undecidable
on 24/10/2016, 00:41:14 UTC
FYI this appears to have been caused by an unexpected/unintended change in the format of partially signed transactions exchanged between the Electrum client and the Trustedcoin API.

A fix for this issue has been deployed to Trustedcoin's servers.  If anyone sees this problem recur, please contact Trustedcoin support .

Sorry to any users who were inconvenienced by this problem.
Post
Topic
Board Electrum
Re: Electrum 2.7.9 Error -> Invalid transaction: invalid signature
by
Undecidable
on 22/10/2016, 07:58:14 UTC
I'm one of the Trustedcoin admins. 

We're still attempting to diagnose this issue. 

Could you retry your transaction?  We've deployed change on our server that may fix it but even if they do not your attempt should generate sufficient diagnostic information for us to isolate the problem.

One other thing worth pointing out is that this error message started appearing with 2.7.9 ... so downgrading may be a viable stopgap option.
Post
Topic
Board Electrum
Re: Invalid OTP
by
Undecidable
on 22/10/2016, 07:24:00 UTC
I tried restoring the seed but was having some troubles with it just greying out.

I'm one of the TrustedCoin admins.

Can you clarify what you mean by "greying out".  Which specific interface element was greying out?

BTW, if you wish to continue this discussion via email feel free to reply via the TrustedCoin contact form.
Post
Topic
Board Electrum
Re: Another 'invalid otp" issue
by
Undecidable
on 08/01/2016, 10:03:57 UTC
I'm the trustedcoin admin. 

From examining our logs it does not appear there is (or has been recently) any problem with our API since other transactions are being processed fine. 

The advice nerioseole gave is spot on.  Jiro, If you are still having problems, feel free to contact me directly via https://api.trustedcoin.com/#/contact-us  ... if you do so please indicate either the email address you used when you signed up or provide one of the bitcoin addresses in your account so that I can find your account.
Post
Topic
Board Development & Technical Discussion
Re: Statistical analysis of Bitcoin public key distribution
by
Undecidable
on 01/10/2014, 21:54:26 UTC
Here's a CSV through block 322933 https://mega.co.nz/#!cRVEUQJA!kkqcVwo6g47hHCA1IkA_JX2r7JHXC4iNBwkRVThZavs

Edit: BTW, these stats only cover p2pkh-type outputs.
Post
Topic
Board Bitcoin Technical Support
Re: Multi-Signature Addresses - Are there online wallet providers that support this?
by
Undecidable
on 04/03/2014, 02:04:07 UTC
actually, i've been running one for a while (that is api-based):

https://api.trustedcoin.com/#/docs

and we have a reference implementation of a web wallet built on top of it:

https://api.trustedcoin.com/wallet/
https://github.com/jseims/trustedcoin-web-wallet
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] NEM -4 billion coins- Equal Shares for ALL - Registration thread (part 2)
by
Undecidable
on 31/01/2014, 11:33:42 UTC
Sent 0.035 BTC; TX: 39f642453c84a6e9b73280d282846a7f4fbace6ed8a0ad65bea3ca0622ae77b9
Post
Topic
Board Development & Technical Discussion
Re: Feedback on P2SH web wallets
by
Undecidable
on 08/11/2013, 05:10:12 UTC
Maintaining Privacy
To maintain maximal privacy, it is important to not re-use bitcoin addresses. However, re-generating such keys repeatedly with each transaction would make many of the backup benefits that come with this system difficult. Users of bitcoin standard addresses already face this problem today and use a variety of deterministic wallet mechanisms to generate multiple keys from a single source.
The same techniques can be applied to the 2-of-3 address. Any key used as a signature should be rotated to a new address based on the next sequence in the deterministic key.

As a compromise solution, the 2-of-3 address offers one more option: only rotating the server's key. Since the 2-of-3 key is generated from 3 keys, one of which is managed by the service, we can rotate the user's funds to a new address by only rotating the server’s key. The resulting address cannot be correlated to the original 2-of-3 address. However, upon spending of the outputs, the public keys will again be revealed and a correlation could be made at that time. To maintain the ability for the user to extract funds without the service, the service will need to send the newly minted service public key to the user for safekeeping. This can be done via email. But again for maximal privacy, use of deterministic key rotation is recommended.

I'm totally with you on multisig for wallet security.  That said, I'm unconvinced these privacy measures are worth the inconvenience they incur vs the benefits of having a stable address.  It will be painfully obvious which TX output is change because it's overwhelming likely to be the only P2SH output ... there are other signals one could incorporate as well but this one alone would likely be sufficient 99% of the time.
Post
Topic
Board Project Development
Topic OP
Trustedcoin.com - a multisignature cosigning web service
by
Undecidable
on 05/11/2013, 22:24:16 UTC
A friend and I put together a P2SH-based multisignature cosigning web service designed to work with bitcoinqt (on both mainnet and testnet). 

The documentation / examples walk through exactly what commands you need to feed to bitcoinqt to pull off 2-of-2 and 2-of-3 multisig using the service as a cosigner.  The service also simplifies spending from multisig addresses since it tracks unspent outputs for multisig addresses (something missing from bitcoinqt currently) and has functions for creating raw transactions just given a "to address" and an amount.

I'd love to hear feedback from anyone interested in multisig on things we could do to make the API more developer-friendly or on policies you think it would be valuable for a cosigner to enforce.  The policies we currently offer are focused around wallet-security use-cases.
Post
Topic
Board Development & Technical Discussion
Re: O(2^80) theoretical attack on P2SH
by
Undecidable
on 02/11/2013, 15:17:36 UTC
 That can be done in work O(2^80) (and massive storage), or various time memory tradeoffs with lower storage and more work.

While work might become feasible, a successful attack on P2SH needs more than a collision: an alternate script valid and redeemable by the attacker.


The attacker uses a 1-of-N multisig redeemScript where the first public key is legitimately his and the other keys (up to 130 bytes) are what he keeps twiddling until he finds a collision.
Post
Topic
Board Service Discussion
Re: Blockchain.info API Problem
by
Undecidable
on 25/10/2013, 21:23:44 UTC
The API supports an "offset" parameter so you can get everything by making multiple calls. 

If I had to guess, they made 50 the maximum allowable value for "limit".
Post
Topic
Board Development & Technical Discussion
Re: Python Bitcoin ECC library, supports signing, Electrum, transactions (no blocks)
by
Undecidable
on 24/10/2013, 21:51:25 UTC
Your problem is that mk_multisig_script returns a hex encoded string and scriptaddr expects binary.  Fix:

Code:
msigaddr = scriptaddr(mscript.decode('hex'))
Post
Topic
Board Bitcoin Discussion
Re: Bitcoin Jokes
by
Undecidable
on 14/10/2013, 04:44:09 UTC
So Secp256k1 walks into a bar and the bartender asks "can I have your order" and the curve group replies "115792089237316195423570985008687907852837564279074904382605163141518161494337"

/rimshot

Post
Topic
Board Beginners & Help
Topic OP
first post
by
Undecidable
on 09/09/2013, 06:14:47 UTC
Hello everyone.  First post and an announcement. 

I created a block explorer for testnet3 http://testnet.btcspy.com/

I made it because http://blockexplorer.com/testnet is usually days behind and btclook doesn't handle p2sh addresses.

Hopefully some other devs find it useful.  Cheers.