What happens if there are no transactions in a block?


This is the previous block,

289790 Number Of Transactions 86 Height 289790 (Main Chain) Timestamp 2014-03-09 23:24:02 Size 43.853 KB

This is the block you are talking about

Number Of Transactions 1 Height 289791 (Main Chain) Timestamp 2014-03-09 23:30:23 Size 0.183 KB

As you can see by the size of the previous block, there was little activity in that time, only 43 KBs worth of transactions, you can also note that both blocks came less than 5 minutes apart, so perhaps the transaction pool was emptied by the previous block and there wasn't enough time for a new transaction to be broadcasted after that. Since every minute counts, miners won't wait for a new transaction to appear because they run the risk to lose the block...

0 0

Short answer is, this can never really happen. Mining is in itself a process of validation where each transaction is checked to make sure of each of two things:

The signatures signing all the inputs of the transaction are valid None of the inputs have already been spent

Once these two criteria are passed, and there is enough of a fee for the transaction to get into a block, it will be mined and be seen by the entire network as a completely valid & irreversible transaction.


At the broadcast level (pre-mining) however, if an invalid transaction is sent to the network it can be rejected by nodes not passing along (propagating) the txn. The nodes propagating will check the transaction for the same two criteria outlined above and then pass it along only if both are met. The caveat here is that depending on where nodes are on the network, if a double-spend is sent through fairly quickly after the original transaction then the nodes that get the...

0 0

What is Dash?

Dash is an online currency which aims to play a dominant role in the cryptocurrency market, along with Bitcoin, covering the privacy and anonymity needs that Bitcoin cannot cover due to its transparent nature.

There is an increasing number of Bitcoin users who do not want their transactions or account balances to be publicly available for everyone to see. Dash will ensure that this doesn't happen by combining the best anonymity technologies and IP obfuscation.

More importantly, Dash is a development platform for new technologies that are gradually integrated to the Bitcoin protocol with the intent to provide additional functionality.

You can read more about Dash here: http://wiki.Dash.eu/wiki/Main_Page

Who is behind Dash?

Evan Duffield (eduffield on bitcointalk.org) is the creator and main developer of Dash. Kyle Hagan (InternetApe on bitcointalk.org) is the Network Engineer of Dash.

Up to June 2014, Duffield has...

0 0

One of the largest sources of confusion in the question of blockchain security is the precise effect of the block time. If one blockchain has a block time of 10 minutes, and the other has an estimated block time of 17 seconds, then what exactly does that mean? What is the equivalent of six confirmations on the 10-minute blockchain on the 17-second blockchain? Is blockchain security simply a matter of time, is it a matter of blocks, or a combination of both? What security properties do more complex schemes have?

Note: this article will not go into depth on the centralization risks associated with fast block times; centralization risks are a major concern, and are the primary reason not to push block times all the way down to 1 second despite the benefits, and are discussed at much more length in this previous article; the purpose of this article is to explain why fast block times are desirable at all.

The answer in fact depends crucially on the security model that we...

0 0

Thanks Mike,
Let me try to explain to you.
Every night, we copy the backup file from Prod and restore it to a staging SQL server. We also create some customized objects on the restored database. Then is will be used as a read-only database to feed a complicated and time consuming ETL process. This staging server datebase is also a data source for couple of reports.
Some times, we need to move the data during business hours. However, we wanted to eliminate the down time during database restore. So we use restore --> reneme technique to reduce the down time.

Here are all the SQL statements in one of the tasks in our SQL Job.



This job has been running for more than two years without problem. However, it failed last...

0 0


Thanks for the article which is very helpful for the beginners like me. I was struggling with some blockings. Can you please help me in that.

There is a small update query which updates all the columns of a particular ROW in a table(Table will have ~20 rows). But that query is blocking. I got the below query from the blockinglogs from a DBA.

curstmt: UPDATE SystemJobTable SET Name = @p0, Description = @p1, Recurrence = @p2, LastStartDate = @p3, LastEndDate = @p4, NextStartDate = @p5, TypeName = @p6, Status = @p7, Enabled = @p8, Server = @p9, ErrorDetails = @p10, Parameters = @p11, CategoryId = @p12, Created = @p13, CreatedBy = @p14, Modified = @p15, ModifiedBy = @p16 WHERE Id = @p17

inputbuffer: (@p0 nvarchar(19),@p1 nvarchar(43),@p2 int,@p3 datetime,@p4 datetime,@p5 datetime,@p6 nvarchar(85),@p7 int,@p8 bit,@p9 nvarchar(14),@p10 nvarchar(4000),@p11 nvarchar(4),@p12 int,@p13 datetime,@p14 int,@p15 datetime,@p16 int,@p17 int)UPDATE SystemJobTable SET...

0 0

Richard Foote wrote:
> "Howard J. Rogers" wrote in message
> news:41a62c19$0$17539$afc38c87_at_news.optusnet.com.au...

>>qwerty wrote: >> >>>Hi, >>>i need explanations about the initrans and maxtrans parameters, in >>>particular what happens when the initrans is exceded when the maxtrans is >>>still respected??. >> >>INITRANS is the *initial* number of transaction slots. It's designed to be >>exceeded on a regular basis. It merely indicates the lowest level of >>concurrency you are expecting for a segment... it doesn't mean Oracle >>isn't expecting you to have higher degrees of concurrency. >> >> >>>For example what happens when initrans = 1 and maxtrans = 100 and the >>>number of transaction on a block is 2, as far i know, oracle can let 2 >>>transaction on the same block if there is enough space in the block in >>>order to kepp track of the transaction. >> >>With INITRANS of 1, one transaction only is guaranteed to be built into >>the header...
0 0

Drupal also supports transactions, including a transparent fallback for databases that do not support transactions. However, transactions can get quite complicated when you try and start two transactions at the same time. The behavior in that case also varies between databases.

A similar problem exists with nesting locks in C/C++. If the code has already acquired lock A and attempts to acquire lock A, the code will deadlock. If you write code that checks if it already has the lock and doesn't attempt to acquire it again, you avoid the deadlock but could release the lock prematurely.

In SQL, we have the same problem. If your code is already in a transaction, starting a new transaction has the surprising and unfortunate consequence of committing the current transaction and starting a new one.

Java solves the nesting problem with its locks by implementing support for a nesting structure similar to what we test below. Java allows you to mark functions as...

0 0