Hmmm....
The un-caused first cause.

Interesting thread! 

Regardless of the accusations of racism, antisemitism, or 'whatever-ism', one only has to look around to see that the modern mainstream media has it's own agenda.
Your statement here is probably true...

Yup!  I couldn't agree more...

It could not be a coincidence.  A simple google search would have shown them the name was already in widespread use.

You can see their filing here: http://tsdr.uspto.gov/documentviewer?caseId=sn87254305&docId=OOA20170307175940#docIndex=0&page=1
You can scroll through the various pages by using the 'next doc' button on the top right of the page  or by using the page chooser under 'document description'.

Now is a good time to buy more.  The price of bitcoin has dropped and bitbean remains fairly stable against bitcoin.  

The increased weight is indicative of increasing health of the network.  There are more nodes in more parts of the world now than there have ever been!  You can see the current positioning of nodes at this cryptoID link (click on the 'Geo-location' button).

Just to clarify, the name change will occur when the current sprint (the release we are working on now) is completed.  However, the old wallet will still work.  The name change will not affect functionality.  Expect to see the name changing on exchanges, but if you elect to keep your old wallet running for now, it will still work.  That being said, the upcoming release will incorporate changes that improve Bean and make adoption easier.

The name change must occur, because a company called 1 on 1 Development has decided to trademark the name and use it for their company/DBA name.  They have very deep pockets and expensive attorneys, so rather than try to fight them in the courts, which would take a lot of money and a lot of our time away from working on improving the Bean, the Bean Core Board of Directors decided to opt for a name change while trying to maintain our identity to the crypto community.

We are still working on it.  There have been some technical issues (bugs) that have arisen with some of the updates, so we are working to resolve those.  

The name change was added onto the already pending release to minimize any disruption.

We appreciate the communities patience while we sort these issues.  

Once we are fully satisfied with the quality control/testing and resolution of any issues, we will release.  We do think we are getting close...

Bitbean does not publish long-term roadmaps per se.  We do publish individual 'sprints' with the most recent stuff we are working on.
The current sprint is posted on http://bitbean.org (near the bottom of the page).
You may find recent announcements at http://bitbean.org/news.html or http://www.bitbean.org/forum/
Announcements are also posted here on bitcointalk and at bitcoingarden, but they quickly become buried due to the nature of the forum software and the sheer volume of interactions.

Yes, Altcoinlover, you are correct.

The idea I was trying to impart is to increase actual connections.  

In fact, my conf file has no nodes listed at all!  The seeder DNS makes that unnecessary now, though I will say that having a few addnode= statements might be helpful in speeding up the initial connection process.
The key information I was trying to give is:

• more beans
• hard-wired ethernet connection (as opposed to wifi)
• port forward port 22460

Check http://bitbean.org/downloads.html.  Scroll down to the bottom.  

You will see Synchronize Your Wallet With the BitBean Blockchain Faster!.

Read this section for full instructions on how to use the snapshot.
The link to the snapshot is small; almost buried in this sentence: "Download this file and save it to the same BitBean folder as the files you kept."
----------------------------------------------------------------------------------------------------------^^^

They will become spendable once they have matured for 100 blocks.  The same as mining for bitcoin, mined bitcoins are not spendable until they are matured, sprouted bean blocks are not spendable.
If you plan to spend all or most, stop sprouting, and wait for the 100 blocks (about 100 minutes since the target block time is one/minute).

Just one thing to add, when splitting a block, if you enter an address and enter the same address for the change address, and send half the selected amount, you can actually send 2 blocks to that address for one fee.

The question of generated but not accepted sprouts occurs a lot.  This info might help.

"generated but not accepted" occurs when you generate a block within a short time (seconds) of another node, and they beat you to acceptance by the network by broadcasting through more nodes sooner.  
The best ways to minimize these occurrences is to:

• increase your sprouting weight
  That is, buy more beans!
• decrease the latency of your connection.
  If you are using wifi to connect to the network, a hard-wired ethernet connection will improve things.  
  If you have a low connection count, creating a port forward on your router, opening port 22460 for incoming connections will allow you to broadcast your generated block through more nodes at once and increasing the chance of "acceptance" (or integration) of your generated block into the blockchain, especially relative to someone with less connections.

First, @grinmoure, be aware that there is some amount of luck involved, the same as mining.  If you wallet says it is sprouting and has an expected time to rewards, you have done things correctly and your patience will be rewarded.

Second, a greater weight of beans will increase your chance of sprouting.

Third, there has been a lot of speculation about optimum block size for sprouting. It depends on how much of your beans you want to spend to do the optimization. (The lead dev of bean has stated many times that 10 - 15k blocks are a good starting point.)  You should be aware, however, that when unlocked and sprouting the wallet will actually self-optimize the blocks over time.  That is it when a block/transaction sprouts, that block is split into 2 blocks of equal value and 500 beans are added to each block.

The reason that smaller block sizes can influence your potential sprouting rate is that when a block sprouts, it is taken out of your sprouting weight until it matures.
For example, if you have one block of beans in your wallet, and they sprout, your weight drops to zero until the 2 new blocks mature and are then capable of sprouting again.  
On the other hand, if you have divided your 400k beans into 100k bean blocks (as suggested by @plasmodesmata), and a sprout occurs, only 100k beans are taken out of the sprouting weight and 300k remain.  Your weight drops but not to zero.

If you are using the minimum resources I listed, the BitBean-qt wallet will use all of it.  Remember, sprouting is essentially mining.  The program is generating and posting the blocks to the blockchain, just like bitcoin miners do for the bitcoin network at an average rate 10 times faster than bitcoin (1/minute). 

I agree with CisColtz, check everything for yourself!  If you plan to use the computer for other things at the same time as the program is running, you may want to add more resources for it. 

You can run other stuff concurrently, but the program will slow down and yield time to other processes, thereby potentially affecting your sprouting rate.

Actually, I agree with your larger point, that anyone may choose to use whichever code-set they choose, and you are absolutely right with your statement regarding centralized development, which is why I applaud the guys who had the fortitude to stand up and present an alternative, knowing they would be accused of all sorts of things along the way.

Your discussion on centralized development is the point I was trying to make, until recently Bitcoin Core had the 'bully pulpit' of the bitcoin world by means of what figmentofmyass was saying.

 

Credibility points deducted.  

This is pure BS!!  Bitcoin Core is a small group of devs who control access to the Bitcoin Core repository (the only bitcoin repository until recently).  They decide what code gets included.  

Just ask Gavin Andresen, or Jeff Garzik about how much control they have.  

This is the kind of thing that happens when people wake up and realize they have been letting a central authority tell them what to do and how to manage their assets.  It's called 'rebellion.' 

As the supposed shepherds of bitcoin (because they control access to the primary bitcoin repository and get to decide which changes to allow), Bitcoin Core overstepped the bounds of authority for a decentralized system by kicking out one of the primary core developers (who tried to fix a problem) and then sitting on their hands and refusing to fix the scale-ability issue for which the masses were pleading.  (I suspect that someone with deep pockets and a strong interest in maintaining the status quo was influencing them.)

So what happens?  A couple of groups of developers, took up the challenge to fix the issue, and since they couldn't get their work incorporated into Core, the only logical choice was to fork the chain, start a new currency, and let the markets/users decide.

Unless there are other major changes, I suspect that we will see a stability develop in which one chain becomes the 'store of value', like gold in a vault, and one will become a truly spendable currency/medium of exchange.

None of these players want to hurt bitcoin.  They just want it to work like they believe it should.  Perhaps they are both/all right...

The recommendation is at least a Dual-core processor (1.2Ghz) with 2 GB of RAM.
Another recommendation is a low-latency internet connection for optimal sprouting.

6 hours


100 blocks

You can read more about it on the github page

Looks like you have a corrupted data file.  Usually this is caused by an improper shutdown or crash of the wallet.

You will need to re-download the blockchain data.  You can speed up the process by getting the latest official snapshot on the downloads page at bitbean.org.
Scroll to the bottom of the page and read the section entitled Synchronize Your Wallet With the BitBean Blockchain Faster! for instructions.
Make sure you have backed up your wallet.dat file before starting this process.

In the future, do not stop your wallet using the close window "X" in the upper corner.  Use the menu "Exit" option.  This is a known bug that is being addressed in the upcoming release.

If you need further help, drop by our team chat.  One of the community members can walk you through the process.