Topic: [ANN] Alloy [XAO] | The Next Generation Anonymous Cryptocurrency - page 5. (Read 27384 times)

Announcement

Dear Community!

This is 1st July official announcement about our progress. I would like to keep you up to date with our current work.

1. We have started developement of electron wallet. Electron wallet is a shell for the Alloy daemon. It is cross-platform (windows, linux, macosx) and will provide us with an easy to use wallet. We will merge our current work on mobile wallet with it, so electron will provide basis for mobile wallet.

2. In last two weeks we have been working on development of "webminer", which will allow for people to mine our XAO coin with CPU from all kind of devices (Pc, phone, tablet). Webminer will be a script embedded in a webpage with a pool selector and % usage selector options. All you have to do is to select pool, intensity, input your wallet address and press start.
Webminer is in testing phase right now and we expect it to be ready in 7 to 10 days.

3. Integration of ethOS support for Alloy coin is almost done, and will be finished in next few days. Next step is simple mining OS support for AMD devices.

4. Our new Youtube channel has been created and updated with first 6 video guides. You can expect more videos to be added soon, also we expect from you some suggestions about which topic you would like to see covered with video.
Alloy Project Youtube channel

5. I am happy to say that job for creation of video intro/closer, posted on our discord channel, is no longer active. We have chosen video intro/closure from our community member
Navneet Jaiswal. Thank you very much for this great intro/closure, that will be used in all our videos. You can see it in each of our videos on our youtube channel.

6. We are also working on our own wiki to add more resources about our Alloy Project. In case you are not sure what wiki is - wiki is a website on which users collaboratively modify content and structure directly from the web browser. By far the most popular wiki-based webpage is Wikipedia.

7. I received confirmation from Cryptobridge exchange, that they will start listing cryptonight coins within 1 months time. Next to being decent exchange, Cryptobridge is also decentralised exchange which is in compliance with our project and idea of bein private and untracable coin. This is another reason that we are interested in Cryptobridge.

8. On our blockexplorer, in pools section we have now also data about pools latency, which is also important information to have when you are choosing your favourite Alloy mining pool. Underneath the pools list there is also "benchmark list" about hash rate with different CPU/GPU - use this as a guide.
Alloy Project BlockExplorer - Pools


I am already looking forward for next announcement on 15th July, because some great news and implementations are coming!
Stay well and keep on following us
Your Alloy Project team

Few people only... I didn't talk much about this with anyone...
It seems you will just need to surrender Anyway don't be too much upset the difference is not so huge...but it can be some 10%
I even tried to mine with 3 threads or 4 threads....and it is working, but hash rate decreased a bit... I was trying this some months ago...maybe if I would give it another go to observe hash rate/power/temps ... At the moment don't have time for it, maybe one day

No, I meant - how many gpus from how many users?
I tried to google and found out there was not much info on that topic.

I have never had problems mining with dual threads. Whenever I use xmr-stak I use dual threads... I have been mining old Cryptonigh, Cryptonight V7 and Cryptonight_Alloy with rx550, rx580 and rx vega64 ...


Yeh, I agree with you about tradeogre... I am pretty much satisfied with this exchange. And the volumes are not so bad...well on alloy are a bit low, but this is not exchanges's fault...on some other coins on tradeogre volumes are very nice

Yes and they just simply don't start without it. Also how could c++ be required for two threads and not for one? That makes no sense.


I stated, you just missed it. "4 gpus each".
And rigs were running with 32 gb for past months perfectly, I raised it to 64 gb for this case, just to be sure. (And it didn't help, of course)

I beleive not every gpu is fit for this exact algo/mining. For example: one of my 580s mines almost everything just fine - I tried it with lots of coins, and it's very stable. But when I run claymore's equihash miner - it also instantly crashes and pc reboots. Still it can mine all other coins AND equihash with other miners. It looks like hardware limitation.

So I think this type of issue could relate to other specific algos/miners. How much statistics do you have on cryptonight two threads mining?

some miners ask for visual c++ in order to work. i dunno about framework since its already being installed in Win10. however you are in win7 so try to install latest framework as well.
now its been a long time since win7. i've even forgot how it were.
i use as swap(virtual memory in windows) 16 gb per card. since you dont state how many cards but you call it a rig i assume its more than 2 cards per rig so try increasing your vram if that's possible.

Tradeogre is pretty good imo -- you can be up and running within couple minutes with no bullshit kyc and the interface is pretty lean. Sure, not too many coins are listed yet, but I guess we'll have to wait and see.

Good day all! I rely that the project will perform all that has been planned!

You seem to be doing everything RIGHT! I have no idea why this wouldn't work for you

I organise gpu_conf like this, but I really don't think this should matter. For double threads It would look like this

"gpu_threads_conf" : [
{ "index" : 0, "intensity" : 432, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true},
{ "index" : 0, "intensity" : 432, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true},
{ "index" : 1, "intensity" : 432, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true},
{ "index" : 1, "intensity" : 432, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true},
{ "index" : 2, "intensity" : 432, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true},
{ "index" : 2, "intensity" : 432, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true},
{ "index" : 3, "intensity" : 432, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true},
{ "index" : 3, "intensity" : 432, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true}
],

Sure.

"gpu_threads_conf" : [
  // gpu: Ellesmere memory:3712
  // compute units: 36
  { "index" : 0,
    "intensity" : 768, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 36
  { "index" : 1,
    "intensity" : 738, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 2,
    "intensity" : 768, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 3,
    "intensity" : 768, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
],


I make 2threads by copypasting one gpu section & lowering int. So it becomes smthng like this:

  { "index" : 0,
    "intensity" : 368, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 0,
    "intensity" : 368, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },

Test!

Hihi, nice description yep this is the beauty of alloy

Hm... everything seems ok. I never install framework and visual c++ on AMD mining rigs, and it works perfectly fine. Can you show me your amd.txt file, and also how you want to do double threads in amd.txt ...

2 rigs, have been working for ~10 month, 4 & 8 Gb ram, 4 gpus each, core2duo & core2quad, win7, drivers from 22.03.2018, 64 Gb swap, how on earth framework could be related to this problem?

Glad to meet the Alloy Project, which allows anyone to send money digitally over our decentralized blockchain instantly, anywhere in the world, to anyone in the world, anonymously

i have a few questions....your rig worked for other coins before or is new new? if its new new, check your risers they can be a pain in the arse
how much ram you have?
what cpu?
how many gpus?
what gpus?
are the gpus all in one machine or different machines?
are you on windows?
is vram enabled for the number of your cards?
is framework and visual c++ installed?
what driver?

hm... that is a dissapointment ... I really don't know why it doesn't work for you, sorry.

Of cause I reduced, more then two times less (i.e. was 890, made 2x390). No go. Tried downclock, overclock, reset settings, up power limit, down power limit - big nothing.

I just realised that I have forgotten to mention, when you use double threads in xmr-stak you must reduce intensity... so for example intensity for single thread is 1000, for double threads will be 600 each.... try reducing intensity alot, and if it works increase it step by step untill it is stable....

Well it's true. Just in case - couple of minutes ago tried 2 threads on single 560 - got instant crash and reboot.