WTB 100,000 XEL @ 0.00023 BTC
I need potential sellers, as I don't have much time to exchange lots of pm's.
PM me for offers.
Please join elastic slack channel https://elasticfans.herokuapp.com/under #trading escrow is byrallier |
|
|
|
Up for sale, Updated available stocks and items for sale.
Hello, interested in Amazon gift cards... Are you still providing source(s)? I don't want carded  Thank you, |
|
|
|
|
I received my btc withdrawal submitted 2 days ago.
|
|
|
|
|
Hello, interested in Amazon gift cards, but need to know the source? If carded, no need to reply.
Thank you,
|
|
|
|
Hi,
Im Kind of new to the blockchain space, so bare with me as im learning as i go. After lurking and reading up on this, I see that this is a very interesting project. Im seeing the only way to get these are by OTC sites that require huge purchases but im not able to spend big. Is anyone willing to send .4 ethereum worth to me? I'll send the you the eth first..
Or i can trade that eth for btc on bittrex if youd like, let me know please.
Please join the slack channel and go to the #trading section, we can help you. I'm online now https://elasticfans.herokuapp.com/ |
|
|
|
Looks like launching the wallet early has been a very positive decision both for the devs and the community at large.
Yes, and I have to say, we've gained a lot of new, dedicated members as a result, too. [Please don't hate me], I sold some of my elastic and the rewards are beyond my imagination (sure we dreamed about the numbers, but until the lite wallet actually launched, they were just that, unrealized dreams). Try to sell to different people if you are selling a small portion to encourage wider adoption. At least until we hit a big exchange, then I believe elastic (xel) will explode based on the interests we've witnessed so far without an exchange and all otc trades. I don't think any other coin has had this much interest without an exchange, someone can correct me... |
|
|
|
would anyone be willing to take the time to sell me around 0.01BTC of XEL? small amount i know, i'm fairly new to crypto and really like this project.
Yes, my friend. join us on elastic slack and give us your slack nick and I'll hit you up, we can do trade for .01 btc |
|
|
|
I have the same question, but I will use what's there now. I will be running an AWS EC2 Elastic node in Tokyo and Seoul with 10,000 coins each to support the network. These 2 regions are becoming important markets for cryptos. |
|
|
|
Yo thanks for the tip but this is a little to technical for me I think  I was lost on the first sentence since I dont know how to create a virtual machine on my pc  Not familiar with linux in any way also. Still leaving my factoids in a wallet without encryption is just not a option for me unless like the paper wallet its not connected to internet in any way. I have to get over myself I guess and start using the paper wallet. Is theyre any way I can check somewhere if my factoids are in my wallet after I send the coins allthough I have the problem that it was connected to the internet if I check it somewhere lol  I have a friend who would understand your post so when he is here I will ask him to look at it. Thanks anyway for your extensive post man. Cheers! You would be amazed how easy it is to run a virtual machine Downloading vmware-player from the vmware website is free (no cost) and downloading the xubuntu.iso is free (no cost) from their website. When setting it up, I allocated 11GB disk space for the vm, 3072MB for ram, and 2 cpu's, so the vm runs well, but that requirement means your host PC has at least 8GB of ram. If you only have 4GB ram, then you can drop it down to 2048MB RAM for the vm or even 1536MB, but if any less, it might be slow. The cpu can also be set to 1 cpu. Xubuntu runs xfce desktop environment which is low demand on resources. Try to run 64bit vm as much as possible... Remember the backup also and to keep in encrypted container (i.e. veracrypt which is also free, I believe, sorry I recommend it and I don't use it as I run linux on the host and vm and luks encryption is part of the os distribution). Good luck and if your friend has questions, I'll try to answer... |
|
|
|
Download vmware player and install xubuntu in a virtual machine. Perform update on the os and reboot.
I was under the impression that a virtual machine protects the host OS from possible malware from within the VM, but not the opposite. Am I wrong? It can be both. The virtual machine is like a separate PC and if it's running linux, then even better. A malware on the vm cannot harm the host, and a malware on the host (assuming windows os) cannot harm the vm, however if someone is able to control your host os, then they can start the vm and do damage, or "steal/copy" from the vm. This would be very visible on the screen but if the host os is running at night and you're asleep, then... The idea is to secure the factom wallet from any malicious copying as it's not password-protected. Running enterprise-wallet in a brand spanking new linux os and installing nothing else but enterprise-wallet using the one line command (well you do have to run the firefox on the xubuntu vm to go to github to download the factom enterprise wallet binary and maybe to run sha256sum to check the hash), voila, you're up and running with a good, clean enterprise-wallet. The other challenge is to connect it to a factomd daemon, but that's a separate worry for now... When the vm is shutdown (recommend to use the xubuntu "start" menu to shutdown after closing the enterprise-wallet application), then the factom wallet is "secure" not open for copying or deleting by anyone. When you need it, just start/power on the vm. [BACKUP (to outside of the vm) is important of the /home/userName/.factom folder to an encrypted container (i.e. veracrypt) as it's not password-protected.] |
|
|
|
Hello,
Are these 2 AWS codes the same event or can each one be stacked 4x each (for a total of 8 )?
EDU_ENG_FY2017_Q1_3_GH_150USD
EDU_ENG_FY2017_Q2_3_150USD
Thank you.
Well this is same event but different quarter and yes it can be stacked with each for a total of 8 . Now when Q3 code releases that you again can add to the same AWS Account also . Awesome! Thank you for the info. Hope you keep selling, these are great for AWS users. |
|
|
|
Hello, Are these 2 AWS codes the same event or can each one be stacked 4x each (for a total of  ? EDU_ENG_FY2017_Q1_3_GH_150USD EDU_ENG_FY2017_Q2_3_150USD Thank you. |
|
|
|
is it more safe to run enterprice locally then online? Started to read the docs going to try to run it locally if its more safe
Both are 100% safe Thanks my wallet is almost synced. Took a few hours is that normal? In the docs they where talking about a waiting time af making a cup of tea? Also I cant seem to find where I can encrypt the wallet? Is it me or cant you really encrypt the enterprise wallet ? You can't encrypt it. That s why I suggest to keep it exclusively on an offline machine. Turn it on only for transactions. Hmm that doesn't sound like anything I want to trust my factoids with.. Going to check out the papermil wallet think thats the best option but I really hate the idea of sending coins to a address where I cant see if the coins are there.. pff but leaving it on polo isnt a option either.. hmm okay thanks anyway for all the tips guys The inability to password-protect the factom enterprise wallet is unfortunate but (imho) it's easy to secure your factoids by running enterprise wallet in a clean linux os environment. Download vmware player and install xubuntu in a virtual machine. Perform update on the os and reboot. To install enterprise wallet is one command "sudo dpkg -i enterprise-wallet-setup-amd64.deb". I don't remember if there are any dependencies needed but I can help if you run into any problems. For the factomd that the enterprise wallet needs to connect to, you have 3 options. 1. factomd on the host machine, 2. factomd on a vps host you own, and 3. (i read a few pages back) factomd on the remote offered by the Factom foundation. I'm running option 2 on an ubuntu vps, but it may not be so easy with updates, plus possible compiling from source, and opening ports on the vps for your enterprise wallet to be able to connect to, etc. option 1 and option 3 are pretty easy, I think. The default gateway for the vm is already set to the host machine. Once enterprise wallet is synced (with any of the options for factomd), perform some small receive and send factoids until you feel comfortable. Backup is important and in that vm, your wallet is in /home/yourUserName/.factom but be very careful if you're going to straight up copy it to the host or to a usb flash, as once again, it is not password-protected. There are options to backing it up to an encrypted volume (i.e. veracrypt) and/or backup the whole vm (the xubuntu has a username/password so the vm does have security with limits) This works for me and still get the peace of mind I have active controls of the factoids I own (able to send and receive as needed) and secure in a vm that has no malware as there's nothing else running or installed on the vm except enterprise wallet plus the xubuntu linux os. ymmv |
|
|
|
....
So i am not in favor of launching a lite-version.
....
We are in a sort of Catch 22 situation and it's good to see the arguments for and against launching being aired. I would argue that by releasing a light version we could attract Devs, testers and PR people to join in the project and help EK and the community to realise the full potential of Elastic, by giving them the opportunity to have a financial stake in it. Anyone that has been reading this thread can see the ridiculous hours that EK is having to put in. Is it right that we continue to expect him to carry this burden alone? Plus, with a bigger team of developers, it might be possible to come up with a timeline for release of a full version. I think it's reasonable to at least put this to a vote within the community. I can see your point. There's another coin (Monero XMR) that I hold and it has a scheduled hard-fork periodically. The development of features (mini-projects) are funded through FFS community efforts using xmr as the currency of payment so there's a built-in share in stake for the success of xel. It's a nice setup and it works as Monero has a lot of features that are being planned and everyone can see what's coming and the funding needed. Some of the projects got funded when xmr was very low USD price, so looking back now, the developers got a nice chunk of value $ but that is part of the appeal of FFS development ($33/xmr atm). We can follow the same path? Have an XEL development fund where people contribute on features to be implemented in the future and all other things that need development (i.e. software gui wallet, mobile wallet, website, etc). I think it's only possible if xel is launched to attract outside developers. The exchanges will support the periodic scheduled hard-forks if there's good volume for the coin (as it brings them lots of profits from trading fees). Hope we can be half as popular as golem... |
|
|
|
Great Seller! I was back again for another $150 AWS code and it worked without any problems. I'll be sad when I've stacked 4 of these, but hey, there's the $100 codes to stack later |
|
|
|
|
Just bought the GitHub EDU $150 and received the code very quick and worked without any issues! What a deal!
My bill last month was $98 so definitely saved me some $$$
I had to wait until my other 2 codes in the account got used up (only have little bit left on one code) so less risk if Amazon takes them out. I'll be back again next month, hope you still have more!
Thank you!
|
|
|
|
Thank you! So complicated... lol. When I do a dumpprivkey on bitcoin, I'm getting a very different type of number L2NLwmubxxxxxdMsHxxxxxxxxxxxxxxxxxx
It's easier if you stay in the hexadecimal and use tools: f9001 + f8c = f9f8d (one can do this without a calculator) and then: $ ./bitcoin-tool --output-format base58check --public-key-compression uncompressed --network bitcoin --input-type private-key --input-format hex --output-type private-key-wif --input <here your hex key the LBC found>
Where bitcoin-tool is https://github.com/matja/bitcoin-tool=> KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rJ5fpCVagTwW (compressed) => 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEtSyptnrHKD (uncompressed) Rico Thank you, Rico. I have another dumpprivkey value that starts with Kxxxx so it's similar. I'll grab that tool on github and play around with it. I'm mining under boholIsland userID. I think this is a great project to test out the limits of our trust in bitcoin cryptography. Even if I find a private key to a $10M wallet, I have no plans to take any part of it. I would not turn down a gift-reward, though, but no conditions attached for the return. Better to have a public project than a secret one... |
|
|
|
..... 2d17543d32448acc7a1c43c5f72cd5be459ab302:u:priv:0000000000000000000000000000000000000000000000000000000000000001 + 0x5e
02e62151191a931d51cdc513a86d4bf5694f4e51:c:priv:0000000000000000000000000000000000000000000000000000000000000001 + 0x65
9d74ffdb31068ca2a1feb8e34830635c0647d714:u:priv:00000000000000000000000000000000000000000000000000000000000f9001 + 0xf8c
3d6871076780446bd46fc564b0c443e1fd415beb:c:priv:00000000000000000000000000000000000000000000000000000000000f9001 + 0xf8c
Rico Hello, how is the private key converted to normal format? Eeasy: f9001 + f8c = 1019905 + 3980 = 1023885 1023885 / 128 = Directory.io Page # 8000 round up to whole number (7999.1015) https://blockchain.info/address/1FMZFP6Esqp41Bp6eJ5FavSwCya5TsWrKm9d74ffdb31068ca2a1feb8e34830635c0647d714 Thank you! So complicated... lol. When I do a dumpprivkey on bitcoin, I'm getting a very different type of number L2NLwmubxxxxxdMsHxxxxxxxxxxxxxxxxxx |
|
|
|
I just updated my LBC and now I'm getting this: Server doesn't like us. Answer: too fast.
I'm using and AMD FX 4300 with ./LBC -c 2 (I even tried -c 1, same result).
Thanks in advance.
What generator is LBC trying to use? I see this file there: gen-hrdcore-sse42-linux64 Did you try a benchmark test? Append -x and see what happens. This is the result: ./LBC -x Will use 2 CPUs. Testing mode. Using page 0, turning off looping. Benchmark info not found - benchmarking... done. Your maximum speed is 3720003547 keys/s per CPU core. What size is your BLF file? 536870912 mar 18 20:39 funds_h160.blf I had this happen before and I just made a new LBC directory and did a clean install. I struggled with this "toofast" problem when I was using the generic 1.031-LBC.bz2 and renaming it. I got it fixed by downloading 170220-b3dc4e1346c597c75b6a879dbc00c9a5.gen-hrdcore-avx2-linux64.bz2 and also 170305-ffb5593f2260d1b4cb0f7e4a990af9e8.blf.bz2 but that's using an AWS EC2 that's running Intel CPU so probably need a different gen-hrdcore file... |
|
|
|
..... 2d17543d32448acc7a1c43c5f72cd5be459ab302:u:priv:0000000000000000000000000000000000000000000000000000000000000001 + 0x5e
02e62151191a931d51cdc513a86d4bf5694f4e51:c:priv:0000000000000000000000000000000000000000000000000000000000000001 + 0x65
9d74ffdb31068ca2a1feb8e34830635c0647d714:u:priv:00000000000000000000000000000000000000000000000000000000000f9001 + 0xf8c
3d6871076780446bd46fc564b0c443e1fd415beb:c:priv:00000000000000000000000000000000000000000000000000000000000f9001 + 0xf8c
... Rico Hello, how is the private key converted to normal format? |
|
|
|
|
Show Posts
