I saw the alpha code on github , but when the Alpha test will be realised ?
which repo?
|
|
|
You have the same issue as another issue, alhtough that is an upstream problem, I helped him solve it this way:
Run electroneumd like this
electroneumd --add-exclusive-node 167.114.229.99
That node is on my server and will always be online
If your using windows 10: open the folder where electroneumd.exe is extracted to. pres shift right click then select open windows powershell. type .\electroneumd --add-exclusive-node 167.114.229.99 that will get the blockchain to sync. thanks for your help. Could not have done it with out your help. [/quote] No worries man, glad to help
|
|
|
A good feature, would be to have a checkbox to enable/disable a pool, without deleting it (i test my pools and stuff for example)
|
|
|
Found a major bug on the firmware.
If by any chance there's a network loss, the fans will stop (since they are not hashing), and the hashing boards willl burnout...
Fried two of them on one D3.... gonna try RMA them
Actually, replicated this on another D3 , and it verifies I assume on the stock firmware the fans keep running if you lose network, but the D3 keeps running trying to hash? Hopefully blissz can get that bug fixed, really looking forward to trying the firmware since these mofos are louder than I expected... On the original, when there's a network loss, the fans spinup like crazy until they find a working pool, hence it's safer, although louder Going to revert to original firmware for now I can confirm the bug. Testing the solution right now. Many thanks for at least take the time filling this bug. I'm very sorry for the loss edit: with the automatic reboot on low hashrate function it won't burn out, but that was was not working on the previous firmware version... No worries man, we all know this could happen x) , I've set two high performance blowers to cooldown the hashboards, and they seem to be working now, go figure x) Glad to help, and thanks a lot for the quick update, gonna try it now
|
|
|
Found a major bug on the firmware.
If by any chance there's a network loss, the fans will stop (since they are not hashing), and the hashing boards willl burnout...
Fried two of them on one D3.... gonna try RMA them
Actually, replicated this on another D3 , and it verifies I assume on the stock firmware the fans keep running if you lose network, but the D3 keeps running trying to hash? Hopefully blissz can get that bug fixed, really looking forward to trying the firmware since these mofos are louder than I expected... On the original, when there's a network loss, the fans spinup like crazy until they find a working pool, hence it's safer, although louder Going to revert to original firmware for now
|
|
|
Found a major bug on the firmware.
If by any chance there's a network loss, the fans will stop (since they are not hashing), and the hashing boards willl burnout...
Fried two of them on one D3.... gonna try RMA them
Actually, replicated this on another D3 , and it verifies
|
|
|
Found a major bug on the firmware.
If by any chance there's a network loss, the fans will stop (since they are not hashing), and the hashing boards willl burnout...
Fried two of them on one D3.... gonna try RMA them
|
|
|
no wallet synchronization. WIN10 (firewall no) electroneumd.exe WARN net.dns src/common/dns_utils.cpp:487 WARNING: no two valid ElectroneumPulse DNS checkpoint records were received set-log 4 (320kb) - https://www.sendspace.com/file/i71159Same For all of you who have issues with sync run electroneumd like this electroneumd --add-exclusive-node 167.114.229.99 That node is on a server of mine and will never go down.
|
|
|
Nice work T(Tomás, Tiago, Teodoro, Tolentino? ) peralta. Now let's just hope Electroneum doesn't end up in a ditch and actually rises up to the be a good thing. I hate to think that I'm wasting my time mining it. Hhahahahaha, Tiago thanks man, it will rise, but there will probably be a dump first because of some investors's frustratio, I for one am totally supporting the project
|
|
|
Screenshot. Daemon doesn`t look to be doing anything? You have the same issue as another issue, alhtough that is an upstream problem, I helped him solve it this way: Run electroneumd like this electroneumd --add-exclusive-node 167.114.229.99 That node is on my server and will always be online
|
|
|
Are you planning any new exchanges in the future?
|
|
|
Thank you for clear instructions.
But when i check the balance in cli wallet, there is nothing and also when i enter the command to view secret and public keys, they are different from those entered. And also when i open gui wallet, after importing the keys file, it doesn`t look like it is synchronizing.
can you post a screenshot of the gui wallet? I'd suggest you to run electroneumd.exe and let it run until it's fully synced and open the GUI wallet afterwards
|
|
|
How do i import from my paper wallet, cli method looks complicated to me...
Unfortunately the GUI wallet doesn't import from paper wallet yet, maybe in the future i'll implement it. As for the CLI it's quite easy actually, considering you are a Windows user , try to follow this steps: 1) Download Official electroneum wallet (or mine , both have the official cli and software included) 2) Unzip it to a folder on your desktop 3) Start -> Run -> cmd 3) cd Desktop/electroneum (or the folder where you've put it in) 4) electroneum-wallet-cli --generate-from-keys WalletName 5) When asked if you want to save the file, say yes. 5) Enter the requested keys that are on your paper wallet 6) Enter a password that you won't forget (although you will be able to recover the wallet later with the paper wallet) Save all the contents to a notepad or a text file and encrypt it and/or save it in a safe location.. Then open the GUI Wallet, select the language, then select the final option and open the Wallet you generated with it, and let it sync, it can take hours. Hope this helps
|
|
|
Any update regarding an official GUI Wallet?
first 2 weeks in December , and they will keep delay so do not be shocked , And if you complain you will be fudding and do not understand anything . SO just wait and do not worry about the money you paid it is in safe hand You have an unofficial wallet working properly here: https://bitcointalk.org/index.php?topic=2444581.new#newYou have support on telegram if needed
|
|
|
This is what I see when open https://my.electroneum.com/ WE WILL BE BACK AS SOON AS POSSIBLE AS YOU KNOW, AFTER EXPERIENCING A REAL, CREDIBLE, SECURITY THREAT, WE CLOSED ACCESS TO THE ELECTRONEUM WALLET SYSTEM AND APP TO ALLOW TIME TO COMPLETELY OVERHAUL OUR SOFTWARE AND NETWORK INFRASTRUCTURE. WE'VE BEEN WORKING CLOSELY WITH AMAZON AWS (OUR NETWORK INFRASTRUCTURE PROVIDERS) AND WE'VE BEEN IMPLEMENTING SECURITY ENHANCEMENTS FROM OUR DISCUSSIONS WITH THEM AND FROM A THIRD PARTY SECURITY CONSULTANTS. AFTER OFFICIALLY BECOMING ONE OF THE TOP 30 CRYPTOCURRENCIES IN THE WORLD ( http://HTTPS://COINMARKETCAP.COM/ ) AND FOLLOWING THE ADVICE OF OUR SECURITY CONSULTANTS, WE HAVE TAKEN THE DECISION THAT IN THE INTEREST OF OUR USERS' SECURITY WE SHOULD APPLY AN ENTERPRISE LEVEL SECURITY AUDIT AND EXTENSIVE PENETRATION TESTING BEFORE RELEASE. WE’VE ENAGAGED THE SERVICES OF A SECURITY AGENCY THAT WORKS FOR THE US DEPARTMENT OF DEFENSE AS WELL AS COINBASE, SPOTIFY, UBER, BLOCKCHAIN AND DOZENS MORE TOP TECH COMPANIES. WE HAVE AGREED TERMS WITH HACKERONE (HACKERONE.COM) IN SAN FRANCISCO, ONE OF THE WORLD'S TOP SECURITY AND VULNERABILITY TESTING EXPERTS. HACKERONE ARE TO CARRY OUT VULNERABILITY AND PENETRATION TESTING OF OUR PLATFORM BEFORE LAUNCH. THE INDICATED TESTING TIMESCALES ARE THREE TO FOUR WEEKS. I'D LIKE TO ONCE AGAIN APOLOGISE FOR THE INCONVENIENCE THAT THIS CONTINUED DELAY HAS CAUSED YOU. WE HAVE DONE THIS IN THE INTEREST OF ALL OUR USERS, AND TO ENSURE WE ARE IN THE BEST POSSIBLE POSITION TO ACHIEVE THE FIRST MASS ADOPTION OF A CRYPTOCURRENCY, AND BE AN ATTRACTIVE SECURE PAYMENT SOLUTION TO COMMERCIAL PARTNERS. Already replied to you in the main wallet thread x) Btw, walled updated and bug fixed: https://github.com/tperalta82/electroneum-core/releases
|
|
|
now anyone can recompile cgminer for me .. from bitmain ghithub dash miner wit this mod chance xcoin.c in groest.c (delete xcoin.c and rename groest.c in xcoin.c) wasting time. read basic of programming. groest.c used in xcoin.c and can't work else. thans but already have that , that not the hexa file for programmer
are U sure? #define PIC16F1704_PROGRAM_NEW "/sbin/pic.txt" int PIC1704_update_pic_app_program_new(void) { unsigned char program_data[5000] = {0}; FILE * pic_program_file; unsigned int filesize = 0,i=0,j; unsigned char data_read[5]= {0,0,0,0,'\0'}, buf[16]= {0}; unsigned int data_int = 0; struct stat statbuff; unsigned char start_addr_h = PIC_FLASH_POINTER_START_ADDRESS_H_NEW, start_addr_l = PIC_FLASH_POINTER_START_ADDRESS_L_NEW; unsigned char end_addr_h = PIC_FLASH_POINTER_END_ADDRESS_H, end_addr_l = PIC_FLASH_POINTER_END_ADDRESS_L; unsigned int pic_flash_length=0; int ret=0;
applog(LOG_NOTICE,"%s", __FUNCTION__);
// read upgrade file first, if it is wrong, don't erase pic, but just return; pic_program_file = fopen(PIC16F1704_PROGRAM_NEW, "r"); if(!pic_program_file) { applog(LOG_ERR,"%s: open pic16f1704_app_new.txt failed\n", __FUNCTION__); return; } fseek(pic_program_file,0,SEEK_SET); memset(program_data, 0x0, 5000);
pic_flash_length = (((unsigned int)end_addr_h << 8) + end_addr_l) - (((unsigned int)start_addr_h << 8) + start_addr_l) + 1; applog(LOG_NOTICE,"%s: pic_flash_length = %d\n", __FUNCTION__, pic_flash_length);
for(i=0; i<pic_flash_length; i++) { fgets(data_read, MAX_CHAR_NUM - 1, pic_program_file); //printf("data_read[0]=%c, data_read[1]=%c, data_read[2]=%c, data_read[3]=%c\n", data_read[0], data_read[1], data_read[2], data_read[3]); data_int = strtoul(data_read, NULL, 16); //printf("data_int = 0x%04x\n", data_int); program_data[2*i + 0] = (unsigned char)((data_int >> 8) & 0x000000ff); program_data[2*i + 1] = (unsigned char)(data_int & 0x000000ff); //printf("program_data[%d]=0x%02x, program_data[%d]=0x%02x\n\n", 2*i + 0, program_data[2*i + 0], 2*i + 1, program_data[2*i + 1]); }
fclose(pic_program_file);
// after read upgrade file correct, erase pic ret = reset_PIC16F1704_pic_new(); if(ret == 0) { applog(LOG_ERR,"%s: reset pic error!\n\n", __FUNCTION__); return 0; }
ret = erase_PIC16F1704_app_flash_new(); if(ret == 0) { applog(LOG_ERR,"%s: erase flash error!\n\n", __FUNCTION__); return 0; }
ret = set_PIC16F1704_flash_pointer_new(PIC_FLASH_POINTER_START_ADDRESS_H_NEW, PIC_FLASH_POINTER_START_ADDRESS_L_NEW); if(ret == 0) { applog(LOG_ERR,"%s: set flash pointer error!\n\n", __FUNCTION__); return 0; }
for(i=0; i<pic_flash_length/PIC_FLASH_SECTOR_LENGTH*4; i++) { memcpy(buf, program_data+i*16, 16); /**/ applog(LOG_NOTICE,"send pic program time: %d",i); for(j=0; j<16; j++) { applog(LOG_DEBUG,"buf[%d] = 0x%02x", j, *(buf+j)); }
send_data_to_PIC16F1704_new(buf); write_data_into_PIC16F1704_flash_new(); }
ret = reset_PIC16F1704_pic_new(); if(ret == 0) { applog(LOG_ERR,"%s: reset pic error!\n\n", __FUNCTION__); return 0; }
return 1; }
The only way to see if this works, would be to make a dump of the pic directly on a programmer, and try to disassemble the hex into ASM. Any godly developers?
|
|
|
I am little confused here ,is this really working ? How to send the coins from paper wallet to this wallet if it's really working ?
BTW still I see below message WE WILL BE BACK AS SOON AS POSSIBLE AS YOU KNOW, AFTER EXPERIENCING A REAL, CREDIBLE, SECURITY THREAT, WE CLOSED ACCESS TO THE ELECTRONEUM WALLET SYSTEM AND APP TO ALLOW TIME TO COMPLETELY OVERHAUL OUR SOFTWARE AND NETWORK INFRASTRUCTURE. WE'VE BEEN WORKING CLOSELY WITH AMAZON AWS (OUR NETWORK INFRASTRUCTURE PROVIDERS) AND WE'VE BEEN IMPLEMENTING SECURITY ENHANCEMENTS FROM OUR DISCUSSIONS WITH THEM AND FROM A THIRD PARTY SECURITY CONSULTANTS. AFTER OFFICIALLY BECOMING ONE OF THE TOP 30 CRYPTOCURRENCIES IN THE WORLD ( http://HTTPS://COINMARKETCAP.COM/ ) AND FOLLOWING THE ADVICE OF OUR SECURITY CONSULTANTS, WE HAVE TAKEN THE DECISION THAT IN THE INTEREST OF OUR USERS' SECURITY WE SHOULD APPLY AN ENTERPRISE LEVEL SECURITY AUDIT AND EXTENSIVE PENETRATION TESTING BEFORE RELEASE. WE’VE ENAGAGED THE SERVICES OF A SECURITY AGENCY THAT WORKS FOR THE US DEPARTMENT OF DEFENSE AS WELL AS COINBASE, SPOTIFY, UBER, BLOCKCHAIN AND DOZENS MORE TOP TECH COMPANIES. WE HAVE AGREED TERMS WITH HACKERONE (HACKERONE.COM) IN SAN FRANCISCO, ONE OF THE WORLD'S TOP SECURITY AND VULNERABILITY TESTING EXPERTS. HACKERONE ARE TO CARRY OUT VULNERABILITY AND PENETRATION TESTING OF OUR PLATFORM BEFORE LAUNCH. THE INDICATED TESTING TIMESCALES ARE THREE TO FOUR WEEKS. I'D LIKE TO ONCE AGAIN APOLOGISE FOR THE INCONVENIENCE THAT THIS CONTINUED DELAY HAS CAUSED YOU. WE HAVE DONE THIS IN THE INTEREST OF ALL OUR USERS, AND TO ENSURE WE ARE IN THE BEST POSSIBLE POSITION TO ACHIEVE THE FIRST MASS ADOPTION OF A CRYPTOCURRENCY, AND BE AN ATTRACTIVE SECURE PAYMENT SOLUTION TO COMMERCIAL PARTNERS. The windows version, like I mentioned, has a bug, I have already fixed it but haven't deployed it yet. And yes the wallet works properly as it uses Electroneum Official Wallet Daemon as a backend. As for the message you got , that is pretty normal, this is not an official GUI Wallet, but a 3rd party made by me.
|
|
|
Hey everyone, the hard drive where I had my windows build environment decided to die, i was not able to push the windows release with the bugfix.
It is fixed, tested, and working on linux. I'll take some time, a day or so to rebuild the windows wallet because of this.
Sorry for the inconvenience!
|
|
|
Electromine is having issues, this would be a good chance to spam us
|
|
|
|