[ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 345.

abbeytim

sr. member

Activity: 438

Merit: 250

Quote from: Minerproffi on September 16, 2017, 02:07:18 PM

Quote from: abbeytim on September 16, 2017, 01:26:38 PM

the other problem i see is if lets say someone with a lot of hashpower wants to manipulate the supply to make price go up on exchanges because they could stop supply by mining faster then sell coins then stop there miner get coins again lower price more supply then repeat

so they could in theory manipulate the price

Explain please, if the stock exchanges wallets are blocked, what difference does it make if you can not replenish or change it? I'm sorry

im talking once exchanges are back on and if they implement the 40mh/s hashrate limit

Minerproffi

newbie

Activity: 30

Merit: 0

Quote from: abbeytim on September 16, 2017, 01:26:38 PM

the other problem i see is if lets say someone with a lot of hashpower wants to manipulate the supply to make price go up on exchanges because they could stop supply by mining faster then sell coins then stop there miner get coins again lower price more supply then repeat

so they could in theory manipulate the price

Explain please, if the stock exchanges wallets are blocked, what difference does it make if you can not replenish or change it? I'm sorry

mimokrokodil

newbie

Activity: 32

Merit: 0

Quote from: pmsk on September 16, 2017, 01:55:05 PM

Remore addnode=... ,insert connect=.... .

Looks like problem is solved, thanks m8! Roll Eyes

pmsk

newbie

Activity: 73

Merit: 0

Quote from: mimokrokodil on September 16, 2017, 01:49:56 PM

I'm having synchronization issues with 1.4.4.1, similarly as with 1.4.3. It just stops (?) loading blocks and indicates "OK" for some time without block number change.
Solution is simple: I need to restart client, and it will successfully load blocks... and stuck again. I have at least 2-6 active connections all the time if that matters.

Ofc done all needed things including loading blockchain (Joe's one) and adding nodes.

Remove blockchain, unpack downloaded blockchain.
Remore addnode=... ,insert connect=.... .

Looks like, you simply download chain from "bad" node and now you cannt download true chain.

pmsk

newbie

Activity: 73

Merit: 0

Quote from: abbeytim on September 16, 2017, 01:04:35 PM

thanks joe for the updates

also the 40 mh/s limit https://poolinfo.systms.org/

currently we are at 100mh/s network and it looks like about 50% of that is solo or unknown hashrate

We talk about this and 300kh/s 2 or 3 weeks ago. Congrats.

mimokrokodil

newbie

Activity: 32

Merit: 0

I'm having synchronization issues with 1.4.4.1, similarly as with 1.4.3. It just stops (?) loading blocks and indicates "OK" for some time without block number change.
Solution is simple: I need to restart client, and it will successfully load blocks... and stuck again. I have at least 2-6 active connections all the time if that matters.

Ofc done all needed things including loading blockchain (Joe's one) and adding nodes.

vascrs11

full member

Activity: 504

Merit: 106

Can someone help me regarding staking?

1. What is the minimum amount of coins required in order to get rewards ?
2. I have updated wallet and blockchain , i enable staking and 1 day now i receive 'Expected time to receive reward is 3 hours'.
3. How can i configure stakesplitthreshold and stakecombinethreshold parameters for better results and what are the default values

Pyroboby7

member

Activity: 94

Merit: 10

Quote from: Digital256 on September 16, 2017, 01:31:24 PM

Is anyone having issues even 'loading' the new 1.4.4.1 wallet?

Using Windows 10 64x and i receive an (Error Loading Block Database) dialog when loading the new wallet, than the app crashes.

I have the updated blockchain bits in the folder, but still receive the above.

Hoping someone else is having this experience and has some guidance on how to resolve.

Are there steps or something that i am missing to make this work? Starting to get really really really annoying....

Did you delete the old blockchain and db folder before putting the new one in?

Digital256

newbie

Activity: 3

Merit: 0

Is anyone having issues even 'loading' the new 1.4.4.1 wallet?

Using Windows 10 64x and i receive an (Error Loading Block Database) dialog when loading the new wallet, than the app crashes.

I have the updated blockchain bits in the folder, but still receive the above.

Hoping someone else is having this experience and has some guidance on how to resolve.

Are there steps or something that i am missing to make this work? Starting to get really really really annoying....

abbeytim

sr. member

Activity: 438

Merit: 250

the other problem i see is if lets say someone with a lot of hashpower wants to manipulate the supply to make price go up on exchanges because they could stop supply by mining faster then sell coins then stop there miner get coins again lower price more supply then repeat

so they could in theory manipulate the price

abbeytim

sr. member

Activity: 438

Merit: 250

the top 5 or 6 miners on that pool are over 1mh/s

abbeytim

sr. member

Activity: 438

Merit: 250

also minerclaim.net
Hashrate    38.90 Mh/s
Workers    708
Efficiency    99.66%

Last found block    1480765
Network block    1480782

is already almost at that limit so will pools just limit how much hashrate u can have

akuci

full member

Activity: 226

Merit: 100

Quote from: abbeytim on September 16, 2017, 01:04:35 PM

thanks joe for the updates

also the 40 mh/s limit https://poolinfo.systms.org/

currently we are at 100mh/s network and it looks like about 60% of that is solo or unknown hashrate

Unknown private pools. A few big miners join up and set up their pool maybe.

abbeytim

sr. member

Activity: 438

Merit: 250

thanks joe for the updates

also the 40 mh/s limit https://poolinfo.systms.org/

currently we are at 100mh/s network and it looks like about 50% of that is solo or unknown hashrate

joelao95

legendary

Activity: 1190

Merit: 1009

Coin of the Magi!

Quote from: deztroyr1 on September 16, 2017, 10:30:27 AM

yay! a new version, new chain and another bunch of lost coins. i hope this stops now. lost quite enough

This is NOT a new chain; this is continuing the prior official chain going with fixes.

joelao95

legendary

Activity: 1190

Merit: 1009

Coin of the Magi!

Quote from: Pyroboby7 on September 16, 2017, 10:41:46 AM

Block generation seems to be slower than expected. Any idea why?

By average, block time is 90.508s, 77.6s and 93.3s for the past 1000, 500 and 100 blocks, they are about in the range.

joelao95

legendary

Activity: 1190

Merit: 1009

Coin of the Magi!

Quote from: joelao95 on September 15, 2017, 01:03:14 AM

The chain data here:

http://coinmagi.org/bin/block-chain/

is not up to date yet (1111331), but I decided not to delay the release. Pls connect to 104.128.225.215 to get sync to the latest block. I'll restart 104.128.225.215 sometime in the morning so that we can have the latest chain / wallet up. Pls connect to the backup server 45.35.251.73 too.

~~I believe we can do "addnode" from now on.~~ ~~Wait until 104.128.225.215 is updated. I'll post.~~

Wallet version v1.4.4.1. All having v1.4.4.0 already running, pls update ASAP.

I've uploaded a chain to

http://m-core.org/bin/block-chain/
http://coinmagi.org/bin/block-chain/

And the chain by ex33s:

https://bitcointalksearch.org/topic/m.21868680

Both servers 104.128.225.215 and 45.55.252.11 are running the latest wallet. We're going toward hardforks at 1481500 and 1482000. The following are what we should use from now on:

Code:

addnode=104.128.225.215
addnode=45.55.252.11

Once we are back on track and the network gets stable, we'll go setting up the following. It won't be a simple diminishing / eliminating, but rather an overall plan on cutoff the overhash which will need get adjustment to PoW rewards, as well as a well-behave and fast-adjustment difficulty algo that is critical to the system. I will post as to how, what we can do and what we are going to do.

Quote from: joelao95 on September 04, 2017, 05:48:49 PM

...
3) Regarding PoW mining, I strongly believe the way we should be heading is the way we are right now. We might need to stick to the big vision, and fulfill the task as much as possible, by getting around the issues, or mitigating the impacts, but not by just turning off the source. From what I can see, without PoW will lead MAGI to nowhere. I propose a check on the PoW blocks on the overall network mining hashrate, say a total of 40MH/s will make all PoW blocks being rejected; in other words, PoW is turned off once network hashrate exceeds the limit, and back to life once below the limit. Until we figure out a better solution, this might help. Let me know the maximum hashrate you'd like.
...

Pyroboby7

member

Activity: 94

Merit: 10

Quote from: abbeytim on September 16, 2017, 10:23:34 AM

Quote from: akuci on September 16, 2017, 10:04:56 AM

ETA for Bittrex wallet unlock?

The follow changes were made with hard forks scheduled to take effect:

0. Sync checkpoint & master server: currently rebuilding blockchain
1. PoW & PoS checking starting at 1481500 (around this Friday night EST)
2. Difficulty adjustment starting at 1482000 (around this Saturday morning EST)
3. Protocol version: 71062, prior version to 71062 shall be disconnected
4. End maintenance mode height: 1481500 (PoW / PoS block reward back to normal)"

so i assume when were end of maintenance mode with no issues joe will tell the exchanges use the software
1480643 is current block recieved so a while to go yet

Block generation seems to be slower than expected. Any idea why?

abbeytim

sr. member

Activity: 438

Merit: 250

this was up yesterday

deztroyr1

full member

Activity: 284

Merit: 100

yay! a new version, new chain and another bunch of lost coins. i hope this stops now. lost quite enough

Topic: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 345. (Read 2375622 times)