All the same as for Windows/Linux EmerCoin Qt
|
|
|
... Закупите им спектрометры и вольфрам не прокатит.
Тут прокатит только ножовка по металлу, ну или мощнейший нейтронный дефектоскоп
|
|
|
Good beginning! Users should have a choice, and we will try to give maximum convenience features on blockchain.
|
|
|
EMC hasn't been listed on a big exchange for more than 1 year. Yes it is, but so what?
|
|
|
господа, пиздуйте в соответствующие разделы со своим социализмом
Бешено плюсую
|
|
|
You are doing great job guys with emc in technical area. It just needs more promotion and more exchanges. About the F@H project, i haven't seen a payment for several days now. It is just me or you made any changes? thanks
Thank you! Unfortunately, I'm the only one who recharges Emerfor lately But understand? EMC coin without premine, thus I have had an equal chance with other participants of the mine. And that means that my reserves, though significant, but limited. Perhaps in the future we shift funding to F@H enthusiasts?
|
|
|
Thanks for the info! We have almost completed the release of the patch.
|
|
|
Потому что вкладываясь в инфраструктуру, инвестор ожидает роста биткойн-экономики. А рост биткойн-экономики неизбежно приведет к росту курса, хоть и с некоторым лагом. А так как инвестор в конечном счёте хочет заработать, оба варианта инвестиций могут рассматриваться.
Нифига, как вложение биткоин крайне рисковый. А инфраструктура - шлюзы, биржи, договоренности - они не зависят от конкретной валюты. Задешевеет биток - ок, тем ниже порог вхождения, на готовую инфраструктуру. Умрет биток - хоть на ХерКоин можно переставить, и все будет работать, будет вращать лопасти мельницы. Вложения не потеряются. Так-как инфраструктура это актив. А вложение в крипту - пассив.
|
|
|
Не 3 млн., а 3 млрд.$ !!!! Но сколько из этого будет использоваться под биткойн, это уже интересный вопрос Ага, 3 триллиона! Лапшу с ушей можно прямо в дуршлаг отбрасывать. Когда все проясниться, вот будет Fuuuuu знатный!
|
|
|
Если там всего 3 млн.$, как пишут выше, то высоко он не поднимет Да, ему сейчас с удовольствием всунут битка. Даже если и поднимет, ничего это не изменит - 99% пользователей просто паразиты, для того и ждут туземуна, чтоб покормиться халявой. Умный инвестор вкладывается в инструктуру, глупый в саму крипту.
|
|
|
Тувемун начался ахахаха! чё то быстро, даже год не прошёл глядишь и с такой регулярностью хомяки разбогатеют Ага, класс! Нашелся инвестор, влошится сейчас поднимая неподъемное.
|
|
|
Another 2 topics that crossed my mind: Is a testnet available? I haven't found any information in this thread nor on the homepage... What are IP addresses of testnet nodes to put into the emercoin.conf? And regarding security: http://emercoin.com/#specs (tab#2 "Security") states For a successful attack on the network, the attacker must accumulate 51% of the computing power, and 51% of M1 aggregate (total coin supply). This task is much more difficult than just to accumulate 51% of the network's computational capacity.
Is the block trust value of PoW blocks significant? I don't remember in which file of the source code to look after the calculation, but as Emercoin seems to be a fork of Peercoin, I'd wonder if the PoW blocks have a significant block trust value... To attack PoS 51% of all actively minting should be enough, right? There is a local testnet which you can create by writing testnet=1 to emercoin.conf. But you will need at least two testnet wallets connected to each other to start mining blocks. Here is an example of two such configs: 1st config: # Run on the test network instead of the real bitcoin network. testnet=1 # server=1 tells Bitcoin to accept JSON-RPC commands. server=1 daemon=1 # You must set rpcuser and rpcpassword to secure the JSON-RPC api rpcuser=testnet1 rpcpassword=testnet1 rpcallowip=127.0.0.1 # Listen for RPC connections on this TCP port: port=9531 rpcport=9532 # add testnet wallet nr 2 addnode=127.0.0.1:9731 2nd config: # Run on the test network instead of the real bitcoin network. testnet=1 # server=1 tells Bitcoin to accept JSON-RPC commands. server=1 daemon=1 # You must set rpcuser and rpcpassword to secure the JSON-RPC api rpcuser=testnet2 rpcpassword=testnet2 rpcallowip=127.0.0.1 # Listen for RPC connections on this TCP port: port=9431 rpcport=9432 # add testnet wallet nr 1 addnode=127.0.0.1:9531
|
|
|
А ЦБ ведь не просто так в феврале на биткоин наехал, они еще тогда запланировали слив рубля и отжимание у электората путина 30-ти процентов. Этим запретом Цб признал, что "денежный суррогат"- биткоин, является более надежным активом, чем "обеспеченный" рубль.
Кстати да
|
|
|
Yes, it's really cool! Do you have anyone in mind? A programmer who is able to write plugins for the browser?
|
|
|
Use EmerCoin NVS to deploy and manage Public Key Infrastructure!Users can manage their own login credentials (public keys) by submitting and modifying records in the EMC blockchain (using the standard EmerCoin GUI or daemon). Similarly, admins can manage user groups for their services that may contain references to other groups as well as individual users - allowing for the creation of recursive authentication trees. Records are considered secure and unalterable due to the nature of blockchain technology. Comparing to the most popular alternative - storing public keys in the LDAP server, this system has the following advantages: - This is first world-wide PKI system. Not just enterprise-level, but real world wide.
- Not needed setup of dedicated LDAP-server(s) as domain controller - info retrieved from local wallet program.
- Impossible situation, when user cannot login to server, because of LDAP server is unavailable or down.
- Impossible situation, when attacker insert into LAN fake LDAP server, and get access to all computers at once.
- Sensitive information retrieved from a wallet locally, and cannot be blocked/intercepted/alerted in the network.
- Easy to configure, no troubles. Just plug and play.
- WorldWidePKI - for WorldWideWEB. System can be used for authentication to another services - e.g. for WWW-servers.
Original - http://emercoin.com/EmerCoin_and_OpenSSH
|
|
|
Nice document! I will update the first post of the topic
|
|
|
Congratulations to the EMC team on this important update. The domain names are already extremely useful!
Is update required? Particularly I am wondering if exchanges must be notified... or is it safe to continue using previous version?
Messy, sorry, I didn't understand from the first time. Sure, to see all new features you have to download the new version.
|
|
|
|