M
MangledBlue
Guest
lol - boom - boom - boom - boom - boom - boom - boom - boom - boom - boom - boom - boom - boom - boom - boom - boom - boom - boom
lol
lol
hahahalol - boom - boom - boom - boom - boom - boom - boom - boom - boom - boom - boom - boom - boom - boom - boom - boom - boom - boom
lol
For anything that does not require wallet - query for blocks, txes etcAnd what would you use this 'feature' for?
right onFor anything that does not require wallet - query for blocks, txes etc
Yep, to spend ix-received funds you need at least one block confirmation. And to ix them from receiver you will need 6.So - in coin control they all say 0 confirm
Meaning that I have to wait to SPEND them
but what iX really does - is - it tells the Recipient that the DASH is GOOD and verified - BUT - you, as a Recipient have to wait to spend it - correct??
C:\Testnet\out.23;32;07.txt (2 hits)
Line 3: "b37afec75251a73ff05ef71e4c5afd9fd37e95dc755177ba624cbfb229d65e89-1" : " ENABLED 70101 yDDoDLvKberiXXwS1hpX72yL7eD9aYT81Q 188.165.84.230:21751 1438926942 -223 1438908084",
Line 52: "1b03acaebe349e07f52b232fb51a52c1a3389af1d6d600cad9830c57835c8afb-1" : " ENABLED 70101 yDDoDLvKberiXXwS1hpX72yL7eD9aYT81Q 188.165.84.230:15180 1438927165 0 1438908060",
You can have multiple masternodes from the same IP because they are on different ports on testnet, on mainnet port=9999 is mandatory.If you issue "masternodelist full" command, search the result for tDash address = yDDoDLvKberiXXwS1hpX72yL7eD9aYT81Q, there are 2 remote MNs running on collateral from one address:
Thing is, one local wallet address was able to start two remote MNs; ie. 1000 coins = 2 masternodesYou can have multiple masternodes from the same IP because they are on different ports on testnet, on mainnet port=9999 is mandatory.
but they have two different ports?Thing is, one local wallet address was able to start two remote MNs; ie. 1000 coins = 2 masternodes
OH..... how does that work? we can't use the same vin for two masternodes, right?They could be different servers, it wouldn't matter... I'm talking about my local wallet address with only 1000 coins is providing collateral for two masternodes
Well, that's why I figured I should mention it...OH..... how does that work? we can't use the same vin for two masternodes, right?
Actually there are 2x 1000 DASH in that tx - do you own both addresses?They could be different servers, it wouldn't matter... I'm talking about my local wallet address with only 1000 coins is providing collateral for two masternodes
Yes I doActually there are 2x 1000 DASH in that tx - do you own both addresses?
View attachment 1702
So what's the issue then?T
Yes I do
K then that's OK, right? Just that masternodelist full shows only one local wallet address running two MNs, that seems odd, no?So what's the issue then?
You have two masternodes running on two different vins out of three available (yDDoDLvKberiXXwS1hpX72yL7eD9aYT81Q has 3x 1000 DASH)
http://test.insight.dash.siampm.com/address/yDDoDLvKberiXXwS1hpX72yL7eD9aYT81Q
It may be unusual to have the same pubkey for two masternodes (most people split their 1000 DASH to unique addresses) but it is not prohibited. You can send 10 x 1000 DASH to the same address and run 10 masternodes from these vins and all will show with the same pubkey.K then that's OK, right? Just that masternodelist full shows only one local wallet address running two MNs, that seems odd, no?
Cool, thanks for explaining... I hadn't seen or heard of that before, so I was kinda surprised when I noticed it.It may be unusual to have the same pubkey for two masternodes (most people split their 1000 DASH to unique addresses) but it is not prohibited. You can send 10 x 1000 DASH to the same address and run 10 masternodes from these vins and all will show with the same pubkey.
No problem - in the end only the vin is what counts, they HAVE to be uniqueCool, thanks for explaining... I hadn't seen or heard of that before, so I was kinda surprised when I noticed it.
I would love to do that, but scratchy's site doesn't let us use the same address for more than one genkey. it would give this message:For sure... instead of thinking 1000 coin address = MN, should be thinking 1000 coin vin = 1 MN.
And if we have multiple 1000 vins each operating a different MN, they could all be same wallet address (pub key).
(Why anyone would want to do that?)
Lol, that's his catch all msg for everything.I would love to do that, but scratchy's site doesn't let us use the same address for more than one genkey. it would give this message:
"ERROR: THERES ALREADY A NODE RUNNING WITH THIS ADDRESS"
That's a good question... if you start-many say10 MNs, there's no way to attribute any particular payment to a specificWith start-many, all payments got to the first address, so how do you monitor payments with that? (yup, I've never used start-many....)
If you want to use just one address for more than one MN on scratchy's cloud, I did it, you can to. For kicks I'm going to see if I can get 10 or more all running with same public key. When I have the procedure down pat, I'll tell ya what I did...I would love to do that, but scratchy's site doesn't let us use the same address for more than one genkey. it would give this message:
"ERROR: THERES ALREADY A NODE RUNNING WITH THIS ADDRESS"
hmmm ... I don't think so. That would be total chaos and be of disservice to the argument. The idea of start-many is to simplify things, not to make it worse. With typical start-many, 1k addresses (each with it's own vin) are created, which makes it easier I guess, but since it's the first address that gets payed, it's kind of like the same situation, you can't really tell from incoming payments from which MN it belongs to.That's a good question... if you start-many say10 MNs, there's no way to attribute any particular payment to a specificaddressvin... haha, just assume I suppose