I'd love to know more about Dapps in Bismuth  HCLivess spoke with us in slack earlier about the 'Dapp' implementation for bismuth. They are not the traditional dapp. Ill try to remember what was explained. Perhaps he will see this and clean my description up. The 'dapps' share timestamps, and blocks with the main chain. But they can operate individually, similar to a 'sidechain'. As an example, you could turn any node into a casino and play games against the 'house'. The node could handle the accounting / audit side for its own clients, but still sharing blocks and timestamps with the main chain. So player 1 plays player 2 (house) in blackjack: player 1 bets 10 BIS on a hand, and loses. Accounting transactions handled on the casino node: player 1 -10 BIS player 2 +10 BIS I THINK this is what was being described... maybe not.. |
|
|
|
WTB bismuth 8500 sats PM
Sold 3000 BIS to Selsonblue for undisclosed price. Can confirm this transaction on my end. Thanks again vikingbill. Still WTB Bismuth @ 8500 Satoshis each -- Buying .75 btc worth |
|
|
|
|
I use mercatox and the exchange is fine. The admin shows up in trollbox as well and bans the nerds.
|
|
|
|
@kpierce77 that's cool if you have experience. I just know a lot of people are clueless. They'll fail at simple tasks like: (g) Challenge response will be a combination of two things:
i. Send a shielded message to SecureNodeHQ containing public t address and
GNUnet document location in message field.
ii. Publish a document to GNUnet signed with private t address including:
A. Public t address of staking Zen, which will also be used for reward
payment.
B. SSL certificate and IP address.
C. Block header from blockchain.
D. Other information that may be necessary to make sure it is a unique
server. Then they'll get upset that they aren't getting payouts This is true. But I believe someone will put together a detailed STIG for nodes. I would help test. |
|
|
|
|
I would like to check out the tradingview suite.
Tradingview ID: CryptoBoardwalk
|
|
|
|
|
Dayum. Copy pasta. Tough world right. Cant back something like this. GL
|
|
|
|
look at your email Boy! you get access to the Platform if you where an Ico investor  BTCI must admit... once you're inside, it does feel quite impressive. First time visiting the ANN since ICO. Tokens still sitting in my wallet growing cobwebs. But after checking out the platform beta a little, I am happy to hold them. PM if you want to sell some OTC |
|
|
|
Considering the state of the market in general, the state of progress, and the market cap of Golem as general reference, I think that any price below 1.5$ is a steal! I honestly think xel should trade way above 2.5$.
Very true, I am updating my offer. 70k @ 50 cents per. It's a steal! Can't believe I haven't gotten more PMs. Updated all open auctions today. |
|
|
|
|
hmm. So every token we buy a baby is born in a third world country and starves to death?
|
|
|
|
|
I liked everything until 4 bill coin supply and 15% premine...
|
|
|
|
i will start mainnet at MAY 30, 2017 utc 00:00 Lol, this is a troll account. |
|
|
|
|
Bounty is growing I see. I am sure it will be much more if the greater community likes the graphics as well. A lot of generous people associated with this project.
|
|
|
|
Now the purchase risk is too large, the private key can not be controlled
Its been like this the entire time... thats why you use escrow as the thread states. People buying OTC understand the risks... if they dont, they will learn them the hard way. |
|
|
|
Hope someone comes up with some Elastic merchandise. From the day I order, I would run around in Elastic jackets waiving Elastic flags out of the windows of my car with a huge Elastic sticker attached to the trunk. Now, back to work If people are interested I can do a shirt / hat order with 1-2 colors and a logo. But first, I will need access to the transparent .psd / vector logo files if someone has them floating around. Then I can produce a few samples and see which ones people like. Edit: Oh shizz i just realized my account turned hero!  Congratulations ;-) Welcome to the Hero Club. Logo Raw-PSD: https://github.com/OrdinaryDude/elastic-core/tree/master/logo-rawIs this the new "official" logo? Seems the logo conversation moved over to the elastic forums without a clear selection. If you want to vote on the logo, or submit a logo, lets keep that conversation over there, and we can hold a formal vote. https://talk.elasticexplorer.org/t/logos-for-elastic/54 |
|
|
|
Hope someone comes up with some Elastic merchandise. From the day I order, I would run around in Elastic jackets waiving Elastic flags out of the windows of my car with a huge Elastic sticker attached to the trunk. Now, back to work If people are interested I can do a shirt / hat order with 1-2 colors and a logo. But first, I will need access to the transparent .psd / vector logo files if someone has them floating around. Then I can produce a few samples and see which ones people like. Edit: Oh shizz i just realized my account turned hero! |
|
|
|
Could a feature like this be added after a first release with basic functionality? Would that require a soft- or hardfork?
In theory, it would require a hard fork. But this is irrelevant, I am adding it now! ;-) Lol, EK you are the man! Hope you get that new ride you deserve brother. Thank you again for being transparent and working super hard on this project. |
|
|
|
|
I do not get any good feelings from this project. But best of luck anyway.
Wont be mining.
|
|
|
|
Got so many ideas ;-)
Maybe we could add an alternative verification method.
Currently we have to limit the program complexity so that the supernodes can run the code in a fairly short amount of time in order to verify if the user actually found a bounty. So basically, the supernode takes the user's input, runs the entire code, and sees if the result is what meets the bounty criteria.
What if we (optionally) allow to check bounties differently? Meaning we allow checking just the result. So it does not matter if the user actually ran the program, or asked some tooth ferry, as long as the value, that the user submitted meets the criteria, it's all right. (Example: sha256d(x) hat 10 leading zeros).
Since we would allow the "calculation" to be disconnected entirely from the "verification", the actual program can be much longer and a lot more complex. Since the verification routine that the supernodes must run is short enough, it's fine.
For this type of work verification, we would have to disable POW payments since it may happen that the program runs 10 minutes or so.
What do you think? These are little things that open up entirely new use cases!
This sounds appropriate EK and could eliminate a potential bottleneck around the verification process. If I am understanding this correctly, you are essentially allowing the calculation queue to be decoupled from the verification queue. So jobs start in order (x,y,z) and the job lengths of L(x=3sec,y=2sec,z=1sec), the first calculations verified would be the first job done with calculations (verification order: z, y, x), not necessarily the first calculation job that went into the queue. Kind of a first come first serve approach to both the calculation queue and the verification queue? A follow up question. Will a user be able to terminate an order if they do not like the approximated lengths of the job? Or will the users be able to dynamically adjust the processing power allocated/purchased for their jobs? Best term i could come up with is something like dynamic processing power allocation(after initial job submission)? Wondering if there is a possibility people start continuously starting/cancelling jobs which could potentially bog down the network. |
|
|
|
Don't use the current git! New features are coming soon And a first real use case. The new feature will be a "storage" for jobs. So jobs can be created with multiple "iterations". This works like this: 1. In the first round bounties are submitted normally. Al bounty submissions have attached a "storage" value - this is basically data that the work author wants to "keep". The storage is filled from within the Elastic PL program. 2. When the maximum number of bounties is reached, the job goes into iteration 2 (and 3 and 4 ...) where the job can reuse the "storage" from other iterations. 3. The job is closed when ITERATIONS*MAX_BOUNTIES Bounties are reached. Why do we need this? Simulated Annealing, Genetic Algorithms, and any other optimization technique which is iteration-based and needs information from the prior iteration. Not sure if the 10 bounty limit is not too low at this point. Will finish the implementation tomorrow, then we can test it! Great update ! Also, very thoughtful functionality to open up usability. |
|
|
|
|
Show Posts
