• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

V12.1 Testnet Launch Thread

Status
Not open for further replies.
I just got a trezor and it's great, but I'm still learning to trust it. What about side channel attacks? Is it possible that a hacked/bugged wallet.trezor.com or a hacked/bugged electrum could show me addresses to send to that aren't really my addresses?

So I just got my trezor, and electrum dash generates a whole bunch of addresses. I copy one of the addresses and send coins there...how do I know with 100% certainty that electrum dash generated that address from the trezor's seed, rather than from some internal hacked or bugged code in electrum?
 
Is it possible that a hacked/bugged wallet.trezor.com or a hacked/bugged electrum could show me addresses to send to that aren't really my addresses?
You could always send a tiny amount first. If after you receive it, you can use the trezor to spend from that input, then you're in control. You can also generate Electrum/Trezor receiving addresses on a completely offline computer, which eliminates the risk of those addresses getting hacked.
 
The entire setup process can be done offline, no account necessary.

The chrome extension can be built and installed on an offline computer (https://github.com/trezor/trezor-chrome-extension) if you want to use Chromium to setup the Trezor.

It is also possible to setup the Trezor with an offline computer by installing python-trezor and Electrum.

@flare is looking into the ability to setup a new Trezor (i.e. initiating Trezor's PIN selection and mnemonic generation process) for an upcoming Dash release, which is great.
There is no mention of any of this in any documentation, anywhere on their website. It's all about pumping you through a web app that cannot possibly be secure or trusted. Thank you for this excellent info.

Python/Electrum sounds like the ticket.

As far as trusting the Trezor hardware itself goes, there are hundreds of pages on bitcointalk dedicated to just that.
I have no qualms about the hardware. It's a setup process that is supposed to be "secure" but forces me to use a webapp and create an account... What kind of absolute fucking idiot would trust that? Are people really this stupid now?

 
:mad:Dag Nabbit!:mad: Did I really never hit enter? Luckily Dash Forum keeps what you typed, LOL:

Can anyone help explain these budget inputs (what they are and where to get them?)

mngovernance prepare:
parent-hash
revision
time = what time in what format?
name
registers-hex

and

mngovernance submit
fee-tx = the tx number for the payment you made in the above step (but please remind how this is done)
parent-hash
revision
time = What time? what format?
name
registers-hex

Thank you.
 
observation 1 :

http://www.ibtimes.co.uk/spectrocoin-adding-dash-exchange-e-wallet-1565767

According to head of finance at Dash, Ryan Taylor, the limit on InstantSend, which is the rebranded moniker of Dash's InstantX capability that allows for near-instant transactions, is 2,000 dash, or about $17,000.

I'm not sure where they got that 2,000 dash for Instandsend, so far i can tell the limit is currently set on 1000 Dash for InstantX ?

56LZssB.jpg


Unless there is a difference between InstandSend limit on Testnet and on Mainnet ?

observation 2 :

running the wallet in windows with commandline option -keypool=10000 seems to replenish the keys to 10000 automatically upon restart, the added "keys left" in overview confirms that.

observation 3 : i'm starting to notice how during sync the syncing indicator has this nice effect where it spins really fast .. i like it.
 
observation 1 :

http://www.ibtimes.co.uk/spectrocoin-adding-dash-exchange-e-wallet-1565767



I'm not sure where they got that 2,000 dash for Instandsend, so far i can tell the limit is currently set on 1000 Dash for InstantX ?

56LZssB.jpg


Unless there is a difference between InstandSend limit on Testnet and on Mainnet ?

observation 2 :

running the wallet in windows with commandline option -keypool=10000 seems to replenish the keys to 10000 automatically upon restart, the added "keys left" in overview confirms that.

observation 3 : i'm starting to notice how during sync the syncing indicator has this nice effect where it spins really fast .. i like it.
yep, it's 1000 DASH on testnet
dash-cli spork show -> SPORK_5_MAX_VALUE
 
You could always send a tiny amount first. If after you receive it, you can use the trezor to spend from that input, then you're in control. You can also generate Electrum/Trezor receiving addresses on a completely offline computer, which eliminates the risk of those addresses getting hacked.

Good points! I finally gained enough confidence that exact way. I sent small amounts to and from the trezor and did so from several different computers. Thank you all for your help!
 
Just thinking.... but it would be nice if automatic backups could be placed anywhere you want them, such as a jump drive or in several locations at once in case of drive failure, but it can be done manually of course, so no biggie :)

I just noticed that the lock wallet and unlock wallet options under settings is no longer there. Why is that please?
 
Just thinking.... but it would be nice if automatic backups could be placed anywhere you want them, such as a jump drive or in several locations at once in case of drive failure, but it can be done manually of course, so no biggie :)
...
https://github.com/dashpay/dash/pull/882
- add new cmd-line option -walletbackupsdir to specify full path to directory for automatic wallet backups
;)

EDIT: not several locations though but anyway :D
 
Oh cool, thanks!

On the other question, did you guys intentionally remove the lock/unlock wallet option in settings on the qt wallet?
 
Oh cool, thanks!

On the other question, did you guys intentionally remove the lock/unlock wallet option in settings on the qt wallet?
I'm not sure what you mean, nothing like tha was removed afaik... Lock/Unlock only visible if you wallet is encrypted though.
 
Merge https://github.com/dashpay/dash/pull/885: Fix mnconflock
Merge https://github.com/dashpay/dash/pull/883: fix GetAnonymizableCredit
Merge https://github.com/dashpay/dash/pull/884: [UI] Transaction Date Range: persistence added and format modified
Merge https://github.com/dashpay/dash/pull/886: also ignore outpoints which are not from currently loaded wallet
Merge https://github.com/dashpay/dash/pull/882: Autobackup enhancements + support autobackup in PS
Hot damn.
 
Status
Not open for further replies.
Back
Top