 Show Posts
|
|
Pages: « 1 2 [3] 4 5 »
|
Can I start mining now?? And the balanced will be safe ?
Do you have exchange in mind where can be listed ?
Good luck !!
Yes, you may start mining. We are not listed at any exchanges at the moment. However, we will reach out to exchanges to initiate conversation in the final weeks prior to the codebase launch. Ahem, so 7% pre mine, 3 days of "betamining" before you make the ann. i think you are being too unfair to yourself. you should be the only miner of your coin.
Not everything revolves around one forum. We launched the announcements to our established userbase on the exact time the beta mine had started, across all social networks. If you don't understand the fundamentals of a premine, continuous development, infrastructure, bounties, partnerships - then you do not have to participate. Cheers. well then let me add. empty github, no public repositories. I can continue but I will rest my case. Also rest in peace uPlexa. |
|
|
|
|
Ahem, so 7% pre mine, 3 days of "betamining" before you make the ann. i think you are being too unfair to yourself. you should be the only miner of your coin.
|
|
|
|
are you crazy ?? mine reward 25% ? premine 20k block and already active 20 MN.. https://prnt.sc/l9ln43next shitcoin yeah, this means all 20 masternodes owned by the team will not only enjoy the premine but also a 25% effective devfee. what a joke! NEXT!!! |
|
|
|
ideal mining? annonce 21000 block!!! ideal for dev aand for sale?
umm, they are giving away coins on telegram quite generously. so i guess not but we will have to see. |
|
|
|
|
seed nodes?
wallet not syncing
|
|
|
|
|
airdrop - seems you have been mining this for over a month now before making an announcement!
|
|
|
|
I just donated 50 ZETTEL, Love ZETTEL.  Thank you. Much appreciated. Working hard on those updates, so keep on mining everybody.  any update dev? just let us know some dates maybe? |
|
|
|
|
an update would be good. communication is so sparse.
|
|
|
|
I've been getting 1 block a day on a 2 Core Celeron. I wouldn't exactly say that is difficult.
Hmm, I'd like to see proof of that please. I've hit it for 3 days solid with Ryzen 1800X and haven't hit 1 block, and 4 days with Ryzen 1700 and no blocks. What hash rate are you at please? My 1800X gets 200Kh/s J 50khs is rate I've been getting on this box. https://imgur.com/a/AUcXsHi, Thanks for coming back to me. First i must appologise, i was a bit "harsh" with my challenge. I genuinely didn't believe your figures. So "Thanks" for proving me wrong, and also for making me re-visit this coin. Below i have posted all my hashrate...clearly the miner doesn't scale versus threads very well, by the time you get to 8 threads it is nearly 10 down, and once i get away from actual cores to threads only, it get worse much quicker. Most unusual for Ryzen. I was expecting with 16 threads more like 400 kh/s. Also interesting, these are for my 1800X, the 1700 figures are exactly the same. (within margin of error). "cryptonomicon25". I have no idea how you are getting 300 kh/s, i can't get that on either PC even O/C ed. That's pretty impressive. One think i have done though, since i had zero blocks (yep, zero from either machine), i have deleted the wallet and roaming on the 1700 PC, re downloaded the wallet from 1st page, and started from scratch. Since your posted 10 hours ago, that PC has now found 1 block. The 1800X i have left on the original files and still no blocks. I will leave it like that for 48 hours. I am wondering, if the wallet has perhaps been recompiled since day 1, or if i just had a bad install (strange it would be bad on both machines). So this way i will be able to see if 1 PC starts to dramatically out perform the other. So all said, looks like we could really do with a more optimised miner. Thanks for making me engage my brain J Ryzen 1800X hashrates (stock) 16GB DDR4 1600 MHz 1 thread - 34 kh/s 2 threads - 68 kh/s 3 threads - 103 kh/s 4 threads - 136 kh/s 5 threads - 171 kh/s 6 threads - 204 kh/s 7 threads - 238 kh/s 8 threads - 250-260 kh/s (34 kh/s * 8 = 272 kh/s) 10 threads - 260-270 kh/s 12 threads - 270-277 kh/s 14 threads - 280-283 kh/s 16 threads - 280-286 kh/s if you look at your hash - the drop is significant after 8 threads. that's usually how ryzen behaves - yours has cpu 8 cores and enables more threads through hyper-threading. most algo hashes are correlated to cores and not threads |
|
|
|
I also agree, I doubt that you have so much bad luck..
My Celeron G3900 with 40 Kh/s finds a block about every 30-35 hours and my two lapis with i7 and 105 kh/s one every 12-28 hours each.
wow you mined it with your i7 laptop, did that to much risk on it? I've done mining this coin with my i5 skylake & got the result of 130 kh/s, on the very begining it just need about 3-5hours to find a block & now it is 12-28 hours with i7 proccesor. the developer or maybe somebody must setup the pool with it, if not then it is not good for this future IMO. if you are getting >=1 block per day then you really don't need a pool. the pool will make enable fractional payments but it'll add up to the same value within a longer time frame. |
|
|
|
I've been getting 1 block a day on a 2 Core Celeron. I wouldn't exactly say that is difficult.
Hmm, I'd like to see proof of that please. I've hit it for 3 days solid with Ryzen 1800X and haven't hit 1 block, and 4 days with Ryzen 1700 and no blocks. What hash rate are you at please? My 1800X gets 200Kh/s J something is wrong at your end then. you should have got/ get many many blocks with your set up. i would suggest trying again now. |
|
|
|
i think dev is mining something else. this was all a ploy to distract folks  |
|
|
|
What's going with website or any further updates? Blockchain has been live a week now with very little additional info. Interested to see in what the development roadmap looks like.
i agree, no news or updates. a sense of direction would help. |
|
|
|
I mine on Ryzen 1600 with 200 kH/s and got nothing in 12 hours  stay at it. difficulty has climbed up and sometimes it takes a long time to find a block but then you might get 2 blocks in a shorter span of time. true randomness |
|
|
|
more than 6 hours mining and zero balance whats wrong  What's your hashrate? The network hashrate is over 60 MH/s, even with a high-end CPU you'd likely find only a few blocks a day. I mine with laptop with 120 kH/s and get 2 blocks in 4 hours, but I get 3 blocks in 4 hours with my server with 80kH/s Speed, it depend on luck I have ryzen 1700 one on windows who get arround 200khs and second on linux with 300khs. Tested with server who has 2 cpu and that easy get 600-700khs so i can say 60mhs is rly low diff for this coin. thats right. ryzen 1950 gets around 560khs on 31 threads |
|
|
|
Like what you are trying to do, but 10 hours in and you have 33MH/s network hash rate, when a typical i5 will give about 100kH/s, so either there are about 300 individual PCs mining or you didn't account for botnets and farms.
Also, running my CPU at 80-90% utilization is not great.
Will come back if this becomes GPU mineable, until then, you're in the hands of the cpu farms my friend.
I don't think CPU farms (or in the future GPU farms) are to be blamed. They are just part of nature. And good for them to achieve that high hash rate. That's not the problem. The real problem I see while looking through the IP-addresses of 500 connections (4 full nodes each fully occupied with 125 incoming connections) is that such CPU farms let each of their computers make a separate connection with an outside full node, so I often see 5 times, 6 times.... 8 times the same IP (but with different port) within the same full node using up available connections that could serve many more people instead. That's the reason why so many complain about not being able to sync. Because that is what takes away much needed open connections from everyone else, and it also doesn't even really serve the CPU farms themselves. They could just as easily have similar results by having all their local nodes in a local network and connect all of them with just one full node (well-connected to the outside) and still achieve the same results regarding block propagation and hash rate. This kind of local centralization might even help them reduce orphan generation (all their sub-nodes will know at the exact same time that work of a new height has to be calculated). So I think I'm going to try the following: I will add some functionality that will allow full node operators to set a limit to how often the same IP is allowed to have incoming connections with them. Full nodes will then be able to automatically deny incoming connections from IPs they already have a set amount of connections with. Something like... setmaxconnectionsfromIP=2 Hmm.... let's see if something like this is already hidden in the code somewhere... those bitcoin devs have lots of stuff lying around in there... lol while i support the idea, you will essentially block some VPNs here. which I guess is okay. we should move this to telegram or discord though. |
|
|
|
whats the block reward?
10 ZETTEL why is the blockreward little less than 10 every time ? |
|
|
|
|
